Skip to content

feat(server): nudge a thread to delegate once it does the work itself - #149

Open
nullStack65 wants to merge 2 commits into
release/native-0.1.10from
feat/delegation-nudge
Open

nullStack65 wants to merge 2 commits into
release/native-0.1.10from
feat/delegation-nudge

Conversation

@nullStack65

Copy link
Copy Markdown
Owner

A thread that does a long piece of work itself never hears that it should have handed it off. Nothing counted the tool calls, and nothing said so.

An opt-in per-thread setting, delegationNudge, counts a root run's own tool calls and reminds the agent to delegate once it crosses a threshold. It is off unless set. The reminder steers the running turn when the provider can take a steer without interrupting the tool in progress, and otherwise waits and is handed to the next run as context. Orchestrator tools such as delegate_task and t3_thread_* are not counted, and a delegation resets the reminders. The setting records who changed it, and a thread cannot change its own.

The counts are on each run in t3_thread_read. The setting is changed with t3_thread_update action set_delegation_nudge, or with the thread.delegation-nudge.set command.

Two shipped providers defer the note rather than steer: Claude's steering interrupts the running tool, and Codex delivers a steer by restarting the turn. The reactor steers only when steering is supported and neither of those is true.

Not enabled anywhere yet. After this deploys, turn it on for the CoS thread (mcp:launch:4c07a2ef8bc6157f99fbae20642807c05a8a57c53eaec25dd4abfa16bc5b242e on environment 2f360b2e-0386-498a-b9cd-62999f3525ba) from a different thread or a client, never from the CoS thread itself:

t3_thread_update
  action: set_delegation_nudge
  threadId: mcp:launch:4c07a2ef8bc6157f99fbae20642807c05a8a57c53eaec25dd4abfa16bc5b242e
  environmentId: 2f360b2e-0386-498a-b9cd-62999f3525ba
  delegationNudge: { enabled: true }

Thresholds are optional and default to 5 and 10.

Model: grok/grok-4.7
Task: feat

🤖 Generated with Claude Code

nullStack65 and others added 2 commits November 20, 2026 20:02
An opt-in per-thread setting counts a root run's own tool calls and, at
each threshold, reminds the agent to hand the work off. It steers a
running turn only when the provider can take a steer without interrupting
the tool in progress; otherwise the note waits for the next run. Off by
default, and a thread cannot change its own setting.

Model: grok/grok-4.7
Task: feat
Agent: Claude Code

Co-Authored-By: Claude Code <noreply@anthropic.com>
A notification that arrives already asking to steer is refused, so the
reminder never reached the turn. Send it queued, the way the other server
notices do, and let the planner steer it when the provider can take it.

Model: grok/grok-4.7
Task: fix
Agent: Claude Code

Co-Authored-By: Claude Code <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 20, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@nullStack65

Copy link
Copy Markdown
Owner Author

Frozen 2026-11-22 CEO portfolio audit — cash-path priority; can reopen at the Dec 18 runway check.

@nullStack65 nullStack65 reopened this Nov 22, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant