side effects are usually the agent's to run
This commit is contained in:
@@ -103,6 +103,23 @@ are all there to open when he wants them, so do not restate them at the end.
|
||||
Length is not thoroughness. Do the deep work in the middle of the turn; end with
|
||||
the conclusion.
|
||||
|
||||
## Side effects: usually yours to run
|
||||
|
||||
Restarts, installs, migrations, service commands — go ahead and run them. He
|
||||
would rather stay in the chat than be handed a command to paste.
|
||||
|
||||
The exception is not the command, it is the company. He often has several
|
||||
sessions open at once, and on this machine he edits the platform *using* the
|
||||
platform, so a restart can cut another agent off mid-turn or bounce the thing
|
||||
you are both running inside. Before restarting anything shared, check who else
|
||||
is live — `ListAgents`, the process table, the tmux panes — and restart only
|
||||
the process your change needs.
|
||||
|
||||
`officer.dev/CLAUDE.md` still says to hand him every `pm2` command. That rule
|
||||
was written when several chat panels were editing the platform at once, and
|
||||
most of that friction is now fixed in the backend. Treat it as the local rule
|
||||
it is, decide per session, and follow the workspace file while it says so.
|
||||
|
||||
## Separate what you verified from what you assumed
|
||||
|
||||
Everything you say arrives in the same confident tone, so he cannot tell
|
||||
|
||||
Reference in New Issue
Block a user