Skip to content

show-me-your-work: name t3_thread_configure, the tool that returns this thread's ID - #79

Open
mr-karan wants to merge 1 commit into
chhoumann:mainfrom
mr-karan:fix/thread-configure-name
Open

mr-karan wants to merge 1 commit into
chhoumann:mainfrom
mr-karan:fix/thread-configure-name

Conversation

@mr-karan

Copy link
Copy Markdown

Why

show-me-your-work tells an agent to get this run's thread ID from t3_thread_configuration. T3 has no tool by that name, so the call fails and the agent has to find the ID another way before it can check its log against the thread.

The tool is t3_thread_configure (apps/server/src/mcp/toolkits/thread/tools.ts in pingdotgg/t3code at d5a50a1). Its description says "Omit threadId for this thread", and with no modelSelection it only reads. The configuration it returns includes threadId.

What changed

  • The substitution rule in tools/substitutions.json that writes this sentence now names t3_thread_configure.
  • The derived show-me-your-work/SKILL.md has the same one-word change, so it stays a derived file and does not become a fork.

The other 15 T3 tools the plugin names all exist in t3code at d5a50a1.

Version

I did not bump VERSION. #72 already uses 2.2.9 and #78 uses 2.3.0, so a third number would only conflict. This can ship in whichever release merges next. If you want it as a release of its own, tell me and I will add the bump.

Checks

  • bun tools/sync.mjs <component> c742dd6 --dry-run exits 0 for pstack, cursor-team-kit and thermos. With the rule change reverted and only the derived file edited, the pstack dry run exits 1 and reports show-me-your-work/SKILL.md as undeclared.
  • bun tools/generate.mjs --check reports 17 generated files current and every check passing.
  • GIT_CONFIG_GLOBAL=/dev/null bun test tests/ --timeout 30000: 546 pass, 69 skip, 2 fail. The 2 failures are both in "the fork check", and they fail the same way on unmodified main on this machine (NixOS, Bun from nixpkgs), so this change does not cause them.

…ns this thread's ID

T3 has no t3_thread_configuration tool. t3_thread_configure with no threadId
reads this thread's configuration, which carries its threadId.
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