Files

kubernetes/apps/ai/t3-code-operator/instance/workstation.yaml

1 ---

2 apiVersion: t3code.janpuc.com/v1alpha1

3 kind: Workstation

4 metadata:

5 name: t3-code

6 spec:

7 serviceAccountName: t3-code

8 resources:

9 requests:

10 cpu: 500m

11 memory: 2Gi

12 limits:

13 memory: 8Gi

14 env:

15 - name: T3_AUTH_PROXY

16 value: "0"

17 - name: T3_GIT_REPOSITORY_SCAN_DEPTH

18 value: "4"

19 - name: TERM

20 value: xterm-256color

21 - name: NPM_CONFIG_CACHE

22 value: /data/npm-cache

23 - name: NPM_CONFIG_PREFIX

24 value: /data/npm-global

25 providers:

26 codex:

27 enabled: true

28 models:

29 - gpt-5.6-sol

30 environment: &gateway-and-memory

31 - name: LITELLM_API_KEY

32 valueFrom:

33 secretKeyRef:

34 name: t3-code-config

35 key: LITELLM_API_KEY

36 - name: MEMINI_API_KEY

37 valueFrom:

38 secretKeyRef:

39 name: t3-code-config

40 key: MEMINI_API_KEY

41 - name: MEMINI_BASE_URL

42 value: http://memini.ai.svc.cluster.local:8080

43 - name: MEMINI_HOME

44 value: personal/jan

45 claude:

46 enabled: true

47 models:

48 - claude-opus-4-1

49 environment:

50 - name: CLAUDE_CODE_OAUTH_TOKEN

51 valueFrom:

52 secretKeyRef:

53 name: t3-code-config

54 key: CLAUDE_CODE_OAUTH_TOKEN

55 - name: LITELLM_API_KEY

56 valueFrom:

57 secretKeyRef:

58 name: t3-code-config

59 key: LITELLM_API_KEY

60 - name: MEMINI_API_KEY

61 valueFrom:

62 secretKeyRef:

63 name: t3-code-config

64 key: MEMINI_API_KEY

65 - name: MEMINI_BASE_URL

66 value: http://memini.ai.svc.cluster.local:8080

67 - name: MEMINI_HOME

68 value: personal/jan

69 config:

70 file:

71 effortLevel: xhigh

72 theme: dark

73 opencode:

74 enabled: true

75 models:

76 - litellm/minimax/MiniMax-M3

77 - litellm/opencode-go/glm-5.3

78 - litellm/opencode-go/glm-5.2

79 - litellm/opencode-go/kimi-k3

80 - litellm/opencode-go/kimi-k2.7-code

81 - litellm/opencode-go/qwen3.8-max

82 - litellm/opencode-go/deepseek-v4-pro

83 - litellm/opencode-go/deepseek-v4-flash-vision-exp

84 - litellm/opencode-go/gpt-5.6-luna

85 - litellm/opencode-go/grok-4.5

86 - litellm/opencode-go/mimo-v2.5-pro

87 - litellm/opencode-go/hy3

88 environment: *gateway-and-memory

89 config:

90 file:

91 "$schema": https://opencode.ai/config.json

92 provider:

93 litellm:

94 npm: "@ai-sdk/openai-compatible"

95 name: LiteLLM

96 options:

97 baseURL: http://litellm.ai.svc.cluster.local:4000/v1

98 apiKey: "{env:LITELLM_API_KEY}"

99 models:

100 minimax/MiniMax-M3:

101 name: MiniMax M3

102 limit:

103 context: 1000000

104 output: 64000

105 opencode-go/glm-5.3:

106 name: GLM 5.3

107 limit:

108 context: 1000000

109 output: 64000

110 opencode-go/glm-5.2:

111 name: GLM 5.2

112 limit:

113 context: 1000000

114 output: 64000

115 opencode-go/kimi-k3:

116 name: Kimi K3

117 limit:

118 context: 1048576

119 output: 64000

120 opencode-go/kimi-k2.7-code:

121 name: Kimi K2.7 Code

122 limit:

123 context: 262144

124 output: 64000

125 opencode-go/qwen3.8-max:

126 name: Qwen 3.8 Max

127 limit:

128 context: 1000000

129 output: 64000

130 opencode-go/deepseek-v4-pro:

131 name: DeepSeek V4 Pro

132 limit:

133 context: 1000000

134 output: 64000

135 opencode-go/deepseek-v4-flash-vision-exp:

136 name: DeepSeek V4 Flash Vision

137 limit:

138 context: 1000000

139 output: 64000

140 opencode-go/gpt-5.6-luna:

141 name: GPT 5.6 Luna

142 limit:

143 context: 1050000

144 output: 64000

145 opencode-go/grok-4.5:

146 name: Grok 4.5

147 limit:

148 context: 500000

149 output: 64000

150 opencode-go/mimo-v2.5-pro:

151 name: MiMo v2.5 Pro

152 limit:

153 context: 1048576

154 output: 64000

155 opencode-go/hy3:

156 name: HY3

157 limit:

158 context: 256000

159 output: 32000

160 model: litellm/minimax/MiniMax-M3

161 small_model: litellm/opencode-go/hy3

162 plugin:

163 - "@eleboucher/opencode-memini"

164 - "@koment/opencode-koment"

165 cursor:

166 enabled: true

167 displayName: Cursor (alpha)

168 grok:

169 enabled: true

170 displayName: Grok (alpha)

171 storage:

172 data:

173 claimTemplate:

174 spec:

175 storageClassName: miroir-fast-local

176 resources:

177 requests:

178 storage: 30Gi

179 workspace:

180 claimTemplate:

181 spec:

182 storageClassName: miroir-fast-local

183 workspaceSharing:

184 smb:

185 resources:

186 requests:

187 cpu: 25m

188 memory: 64Mi

189 limits:

190 memory: 256Mi

191 service:

192 type: LoadBalancer

193 loadBalancerSourceRanges:

194 - 192.168.69.0/24

195 annotations:

196 lbipam.cilium.io/ips: 192.168.69.56

197 external-dns.alpha.kubernetes.io/hostname: t3-smb.janpuc.com

198 git:

199 userName: janpuc

200 userEmail: janpuc@proton.me

201 githubUser: janpuc

202 credentialSecretRef:

203 name: t3-code-config

204 key: GH_TOKEN

205 signingKeySecretRef:

206 name: t3-code-git-signing

207 privateKeyKey: id_signing

208 publicKeyKey: id_signing.pub

209 tools:

210 - name: koment

211 backend: github:koment-dev/koment

212 version: "3.2.0"

213 drain:

214 timeout: 10m

215 timeoutAction: Force

Pairing tokens are one-time and expire in 5 minutes

gotcha ·ok L15

Keeping the auth proxy off means every browser and phone must pair, and the startup banner is a trap for how that is done.

The token printed at boot is single-use. The first client consumes it, in practice the T3 Code Desktop app, and every later attempt fails with "The one-time pairing token was already submitted." That reads like a broken deployment when it is just a spent token. `t3 auth session list` tells the two apart: an existing session proves pairing works.

Do not restart the pod to get a new banner. Mint one from inside the runtime container:

Show the rest

t3 auth pairing create --ttl 2h --label Cluster --base-url https://t3.janpuc.com

The default TTL is 5 minutes, which is not long enough to walk to a phone. `--base-url` prints a complete `/pair#token=...` link on the public hostname; without it the banner prints the pod IP, which no client can reach, and the pair page can fail with "This pairing link is missing its backend host or token."

`--label` names the *client session*, not the environment. It shows up as the first field of `client:` in `t3 auth session list`. The environment name the client displays comes from `machineInfo.prettyHostname` on this Workstation instead.

Sessions are durable: 30 days, listed and revoked through `t3 auth session`. Pairing is a per-device one-off, not a per-visit login.

2026-08-2501M0W6RXGMZSC058473WH6H4SZ

This name is the environment label every T3 client displays

why ·ok L3

The object name is the environment name. t3-code-operator 0.2.0 defaults `machineInfo.prettyHostname` to the Workstation name, so this file no longer sets it and the name in `kubectl get workstations` is the name in the T3 client picker. Renaming the object renames the environment.

Show the rest

Without a value the client falls back to the pod name, which changes on every rollout, so the same backend would appear under a new name after each deploy. T3 resolves its `ExecutionEnvironmentDescriptor.label` on Linux by reading `PRETTY_HOSTNAME` from `/etc/machine-info`, then `hostnamectl --pretty`, then the raw hostname — verified against t3 0.0.38 on 2026-09-04, which still has no environment variable override. The operator writes the label into `/data/t3-coded/machine-info`, which the runtime image symlinks to `/etc/machine-info`.

Set `spec.machineInfo.prettyHostname` only to display something a DNS-label object name cannot spell, such as mixed case or spaces. This deployment deliberately does not: "Cluster" was the old app-template value, and matching the Kubernetes object name is worth more than the prettier string.

2026-08-2501M0W6S8D78B6X1NW96NQ9XW6N

Agents here commit, sign and push as a real human identity

invariant ·ok L198

This block gives every agent on the Workstation the ability to author, sign and push commits that GitHub attributes to a person, not a bot. Treat it as a credential boundary.

Show the rest

Three pieces make that work together. Commits are authored as `janpuc <janpuc@proton.me>`, so GitHub attributes them by email. They are signed with the ed25519 key from 1Password (`signingKeySecretRef`), registered on GitHub as the `claude-code-agent@home-ops` signing key, which is why they render **Verified** rather than merely claiming the identity. Pushes authenticate with `credentialSecretRef`, the `janpuc` PAT carrying `repo` scope, so they reach every repository that account can write.

Signing every commit is deliberate. An unsigned commit from this pod would still be attributed to the human by email while being indistinguishable from a forgery, so signing is what makes the attribution meaningful. The operator writes the git config, the key and `allowed_signers` from the two secrets, so nothing can drift from what 1Password carries.

The consequence worth stating plainly: an agent that acts on untrusted repository content can push signed, verified commits under a human identity. The signing key is separate from the human's own laptop key, so it can be revoked on GitHub independently without disturbing local signing. That separation is the containment mechanism and should be preserved.

2026-08-2501M0W7M7HRMTMJ49DAVFHMRPHG

The data claim stays operator-managed; kopiur backs it up

why ·ok L171

This keeps the live claim `t3-code-data`, which the operator created for this Workstation with a Retain policy and which holds the Codex device login, the Claude and OpenCode homes, the extension cache and the koment tool install. The first draft of this cutover pointed `existingClaim` at a kopiur-populated PVC named `t3-code`; the review showed that Restore would resolve to nothing and hand back an empty volume, silently abandoning `/data` while the retained old claim sat unreferenced.

Show the rest

The operator adopts a retained claim across Workstation recreation, so even a delete-and-recreate of this object keeps the data. 30Gi and the class are spelled out although both match the live claim and the class is the cluster default: the size must not shrink below what exists, and a default class has moved before in this cluster.

Backups come from `backup.yaml`, a SnapshotPolicy on the claim, instead of the `kopiur/backup` component. The component wants to create the PVC itself with a Restore populator, which would fight the operator for the claim; a restore into this claim is therefore a manual Restore with a `pvcRef` target while the Workstation is scaled away.

2026-09-0501M1R1JCCYYG8P2HQ5MMJ7R8Q0