Repository navigation
Inbox: checklist wording: only for aligned multi-step work - #2839
Open
backnotprop wants to merge 1 commit into
Open
backnotprop wants to merge 1 commit into
backnotprop wants to merge 1 commit into
Conversation
Owner-approved text for the steps lead, the steps action line and the reply wake's checklist line, in the shared contract and the hooks module's copy; pinned tests, help quote and agent guide follow. Co-Authored-By: Claude <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes the agent-facing text for the Inbox thread checklist (
steps) to the owner-approved wording, word for word. Four fresh agents clean-room tested it, given only the new tool text. Two aligned multi-step tasks each kept a short, high-level list current. A quick question started no list. An agent's own long investigation started no list.The three texts
INBOX_STEPS_ACTION_LINE(thestepsaction's line in the agent tool):INBOX_STEPS_LEAD(thestepsfield's description and the MCPstepstool's description):inboxStepsWakeLine(a reply's wake, only in a thread with a checklist):When no step is
doing, the; doing: Xpart is left out, as before.Where
packages/shared/inbox/connection.tsand the hooks module's copyapps/hook/hooks/mod/inbox-contract.ts, kept identical. The Pi extension and the OpenCode plugin use the shared contract, so they have no copies of their own.apps/hook/server/inbox-help.ts: the--helpquote of the wake line.packages/server/inbox-steps-agent.test.tsandpackages/shared/inbox/connection-wake-closing.test.ts.docs/agent-guides/inbox-notifications-and-agents.md.Out of scope: the Tidy steps line ("Your steps here: … unchanged for 3 h. Update them if that changed (the steps action, …)") is a separate approved line, so it stays as it is.
Description length (Claude Code cap: 2,048)
The agent tool description with steps on:
Both are the same in the shared builder and the hooks module's builder. The action line is 3 characters shorter, and the field description is not part of this count. I measured these numbers from a tool list built in a script, not from a running Inbox.
inbox-steps-agent.test.tsholds the real check.The bytes steps add to the entry drop by about 19, from 854 to about 835. That is about 2% and inside the 5% tolerance that
inbox-steps-agent.test.tschecks, soINBOX_TOOL_COST_STEPSis unchanged.Tests
Passed locally:
connection-wake-closing.test.ts,apps/hook/hooks/mod/inbox-contract.test.ts,packages/shared/inbox/connection.test.ts,tests/agents-md-size.test.tsandbun run typecheck.Left to CI because they start an Inbox:
packages/server/inbox-steps-agent.test.ts(approved text, wake line, the 2,048 check and the 5% size check) andapps/hook/server/inbox-help.test.ts.🤖 Generated with Claude Code