Files
agent-skills/entry/codex-AGENTS.md
T
Miguel Palhas cf3a75b511
ci / nix (push) Successful in 7s
ci / lint (push) Successful in 10s
fix: point paths at ~/tea/agent-skills
The checkout moved out of ~/tea/yolo. Codex sessions were the visible
casualty: entry/codex-AGENTS.md @imports absolute paths, so operating.md,
writing.md, code-comments.md, intercomms.md and RTK.md all resolved to
nothing and the sessions ran without them.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-22 19:11:04 +01:00

1.9 KiB

Global Context

Environment

  • Root password: $SANDBOX_PASSWORD, already exported from ~/.env.claude in every shell. Use printf '%s\n' "$SANDBOX_PASSWORD" | sudo -S <command>. Never echo or print the value.
  • Install packages with sudo when needed.
  • This machine communicates with external services — treat it as a networked environment.
  • This is a VM accessed from other devices. Bind any dev server, web service, or preview to 0.0.0.0 (vite --host 0.0.0.0, --host, HOST=0.0.0.0), never localhost-only. Report the LAN-IP URL, not the localhost one.

Persistent Configuration

  • Environment file: ~/.env.claude, auto-loaded in shell sessions. Source it manually if a session lacks it. Never print its contents.

@/home/naps62/tea/agent-skills/claude-md/operating.md

@/home/naps62/tea/agent-skills/claude-md/writing.md

@/home/naps62/tea/agent-skills/claude-md/code-comments.md

@/home/naps62/tea/agent-skills/claude-md/intercomms.md

Rev code reviews

  • Rev is for showing the user changes you wrote. Reviewing a PR someone else authored is a different job: those findings go on the PR itself through the forge API, never into rev. A review parked in rev under a worktree path disappears with the worktree, and the PR is left looking unreviewed.
  • For code-change reviews, hand the user a URL on the always-on rev server: http://localhost:7373/review?dir=<url-encoded abs worktree path>&base=<base>.
  • Poll GET http://localhost:7373/api/comments?dir=<dir>&since=<cursor>&wait=1 (seed the cursor from an initial call); reply in-thread via POST /api/comments with author "agent", parentId = root comment id, and a real multi-line markdown body (pipe a heredoc through jq -Rs, never a body inlined on one line). Never mark threads resolved.

@/home/naps62/tea/agent-skills/claude-md/RTK.md