fix(startup): add actionable instructions to assigned beacon
Polecats were burning 48k+ tokens on exploratory work when spawned because the startup beacon was informational-only. By the time the propulsion nudge arrived 2 seconds later, the agent had already started exploring. The handoff topic already had explicit instructions; this adds the same pattern for assigned work: "Work is on your hook. Run gt hook now." Fixes #319 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -75,5 +75,11 @@ func FormatStartupNudge(cfg StartupNudgeConfig) string {
|
||||
"4. If nothing hooked → wait for instructions"
|
||||
}
|
||||
|
||||
// For assigned, work is already on the hook - just tell them to run it
|
||||
// This prevents the "helpful assistant" exploration pattern (see PRIMING.md)
|
||||
if cfg.Topic == "assigned" {
|
||||
beacon += "\n\nWork is on your hook. Run `gt hook` now and begin immediately."
|
||||
}
|
||||
|
||||
return beacon
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user