Original Summary

My Claude Code workflow usually involves... a lot of subagents. I make one Opus model coordinate work as my tech lead, it dispatches subagents using models appropriate for the task into their own git worktrees, and then I try to multitask and do something else while they run.<p>I&#x27;d been finding lately (particularly with Opus 5.5) that there was a ton of drift and instances of subagents not doing anything and it was evading the attention of the TL despite the instructions I gave it to have them report in at a regular cadence.<p>Running tracon in a split terminal is my new personal workflow. It gives me early indicators when things start going off the rails (ex. blocked on a prompt, idle, looping on a failing command, simultaneous edits to files other subagents are editing, drifting off the brief, etc.) and I can interrogate the subagent&#x27;s workflow and by pressing n the main agent gets a note to make a call on how and if to correct it.<p>Read-only and runs on your machine: it tails transcripts in ~&#x2F;.claude&#x2F;projects&#x2F; and checks each worktree with ps, lsof, and git -- only thing that leaves your machine is what the Haiku judge reads for classification (or optionally you can turn that off with --no-judge).<p>I&#x27;ve found it super useful for the game I&#x27;m building and figured others in the community might also find it useful.<p>If you just want to give it a spin without committing:<p><pre><code> uvx tracon --demo </code></pre> macOS and Linux, Python 3.12+, MIT. (Not affiliated with Anthropic.)

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Hacker News 新项目
  • 发布时间：2026/10/12 03:35:33