feat(agent): enable RTK for docker-git agents#283
Merged
Merged
Conversation
Member
Author
|
RTK scope clarification: This is not GitHub-only. Local rewrite checks on this branch: rtk rewrite 'gh issue view 266'
# rtk gh issue view 266
rtk rewrite 'docker ps'
# rtk docker ps
rtk rewrite 'tsc --noEmit -p tsconfig.json'
# rtk tsc --noEmit -p tsconfig.jsonIt is also not an arbitrary-command firewall. Unsupported commands intentionally pass through unchanged: rtk rewrite 'echo hello'
# no rewriteSo the exact guarantee is: Claude/Gemini/OpenCode hooks route supported command families through RTK ( |
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #266.
DOCKER_GIT_RTK_ENABLE=1|0opt-out documentation and nested docker-git propagation.Proof that agent commands route through RTK
Local verification on this branch:
Temp-home install proof with the same commands rendered by the entrypoint:
Observed RTK artifacts:
.claude/settings.jsoncontains hook commandrtk hook claude..gemini/hooks/rtk-hook-gemini.shcontainsexec rtk hook gemini, and.gemini/settings.jsonpoints to that hook..config/opencode/plugins/rtk.tscallsrtk rewrite ${command}before tool execution.docker exec -u <sshUser>and exportHOME=/home/<sshUser>plusCODEX_HOME, then source/etc/profile,/home/<sshUser>/.ssh/environment, and/run/docker-git/agent-env.shbeforeexecing the agent command.Important boundary: RTK 0.39.0 does not provide a native Codex hook.
rtk init --helpdocuments--codexasTarget Codex CLI (uses AGENTS.md + RTK.md, no Claude hook patching). So Claude/Gemini/OpenCode have technical hook/plugin routing through RTK; Codex is RTK-instruction based until upstream RTK ships a Codex hook.Verification
bun --cwd packages/api test tests/agents.test.tsbun run --filter @effect-template/api typecheckbun run --filter @effect-template/api lintbun run --filter @effect-template/api buildbash -ngit diff --checkbun run checkbun run buildbun run test