ai-sandbox: rotating Git source credentials changes the sandbox key
@AlemTuzlak ci sta già lavorando.
Dal 23/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
TanStack AI version
@tanstack/ai@0.58.0, @tanstack/ai-sandbox@0.5.12, @tanstack/ai-sandbox-docker@0.3.2 (npm latest versions when tested).
Framework/Library version
No UI framework. Bun 1.4.2 on Linux.
Describe the bug and the steps to reproduce it
Changing only gitSource({ auth: { token } }) changes the sandbox instance key, even with the same threadId, sandbox ID, repository, and reuse: 'thread'.
This comes up with GitHub App installation tokens, which expire after one hour. Renewing the token changes the lookup key, so a later run cannot find the previous sandbox record even if its container is still available.
To reproduce, download the three files from the gist below and run:
bun install
bun repro.ts
The script computes keys before and after changing a Git token, then does the same for a workspace secret. It does not create a sandbox or make any network requests; no Docker daemon or real credentials are needed to run it.
Actual output:
Git token rotation changes key: true
Workspace secret rotation changes key: false
Expected: both comparisons return false. Renewing a credential with equivalent access should not by itself invalidate sandbox reuse.
In computeWorkspaceHash(), workspace.secrets is excluded, but source.auth.token remains in the hashed object. gitSource accepts a string token and bootstrap forwards it directly to handle.git.clone().
The provisioning guide documents SecretRef authentication for gitSkill, but the main workspace source does not accept it. Is there a supported way to use rotating credentials for the main Git source without changing its sandbox key?
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
https://gist.github.com/HCaupert/c42a7faf5b38dec95d43b0aa98abc501
Terms & Code of Conduct
- I agree to follow this project's Code of Conduct
- I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
- Lingua principale
- TypeScript
- Stelle
- 3.1k
- Fork
- 331
- Merge medio
- 1g 10h
- PR unite (30g)
- 130
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di TanStack/ai
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
has-pr waiting-on: maintainer
-
Client tools never execute against spec-compliant AG-UI servers (plain `success` RUN_FINISHED) Apertawaiting-on: maintainer
-
has-pr waiting-on: maintainer
Difficoltà 3/5 1-2 giorni Idoneità per principianti 70/100
-
waiting-on: maintainer
Issue simili
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Crush Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
ElementsProject/cln-application#167 · 1 commento · 1 reazione ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
Quantco/pnpm-licenses#17 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100