The best way to control Claude Code, Codex and more from any computer or phone
docs(agents): name the fast commands and stop polling (#22711)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Theo Browne committed
Oct 21, 2026 at 00:12 UTC
73daccf4ec123e8a98f84a09e8a5b6372852c9c6
1 file changed
+5
-2
AGENTS.md
+5
-2
@@ -83,6 +83,7 @@ The most common defect in this repo is a change that works on the path you teste
83
- Sharing over the tailnet is three steps: run `vp run dev --share` in the background, wait for the `pairingUrl:` line in its output, then give that full URL to an unpaired browser. Do not wire up `tailscale serve` by hand, open the URL yourself, or consume the user's pairing link. A browser with the reusable dev cookie can use the bare origin. If a normal one-time token was consumed, mint a fresh one with `node apps/server/src/bin.ts pair`. It carries standard scopes, while the startup URL carries admin scopes needed for Connections settings.
84
- To reuse web dev auth across worktrees, configure one fixed `T3CODE_DEV_AUTH_TOKEN` in the main checkout's gitignored `.env`. The `t3.json` setup links that file into worktrees. Never commit or publish the token or a startup URL. See [Reusable dev credential](docs/operations/development.md#reusable-dev-credential).
85
- Stop what you started, by the PID you tracked. See rule 1.
86
+- Need a second checkout? `git worktree add` it next to this worktree, not in `/tmp`. Remove it when done.
87
88
## Test data
89
@@ -95,7 +96,9 @@ An empty database is a bad test. Seed your worktree's `.t3` with a copy of real
96
97
## Verifying
98
98
-- Smallest proof that the change works. `vp test run <files>` for the tests you touched, targeted lint and typecheck for the scope you changed.
99
+- Smallest proof that the change works. `vp test run <files>` for the tests you touched (`-t "<name>"` in big files), `vp lint <files>`, and `vp run typecheck` in the package you changed. Not `npx tsc`; it is 3x slower than tsc-rs.
100
+- Run `vp run knip:check` (about 35 s) when you add, remove, or rename exports, files, or dependencies.
101
+- Run `node -e` snippets from `apps/server` or the owning package. `effect` does not resolve from the repo root.
102
- Test meaningful logic or observable behavior. Do not render components to static markup to assert props or attributes, or add tests that merely assert callback wiring or mirror the implementation.
103
- **Do not run repo-wide checks.** No `vp check`, no `vp run -r test`, no `vp run -r typecheck` unless I ask. CI owns the full suite.
104
- Backend behavior changes ship with focused tests for that behavior.
@@ -137,7 +140,7 @@ For authorized mobile verification, a missing or outdated native client is a bui
140
- UI changes need before/after images. Motion or timing needs a short video.
141
- Upload PR evidence to GitHub. Never commit PR-only screenshots or assets such as `.github/pr-assets/`.
142
- One request is one PR. Split it only when the maintainer asks. Outside contributions follow the stricter [one problem per PR](CONTRIBUTING.md#one-problem) rule.
140
-- When babysitting: poll checks and comments newer than the last push, verify each bot finding against the source, fix real ones, dismiss false positives with a written reason. Stay quiet when nothing is new. Stop when the bots are green on the latest commit.
143
+- When babysitting: call `watch_pull_request` and end your turn. T3 Code wakes you on checks, comments, or conflicts. Do not poll or sleep. Verify each bot finding against the source, fix real ones, dismiss false positives with a written reason. Stay quiet when nothing is new. Stop when the bots are green on the latest commit.
144
145
## Documentation
146