AIToday
Large Language ModelsZenn AI/MLPublished: Nov 6, 2026, 19:01 JST

Claude Code as task boss: answers shrink to "41 OK"

Send on LINE
Claude Code as task boss: answers shrink to "41 OK"

3 Key Points

  1. What happened

    Shimmochi runs a Claude Code "commander" agent that rebuilds his task list from GitHub and Notion, decides the order, and queues only decisions needing a human into a self-made Orca panel.

  2. Why it matters

    The agent handles handoffs and records, so his main work is answering queued items with a number and a word, and he no longer scans a task list himself.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The setup is built around one deliberate brake: the commander stops before anything touches other people's eyes. Workers' pull requests pause before being shown to other reviewers, and reviews of colleagues' PRs pause before posting, while everything up to that point runs on its own. Below that line, ordering is also delegated — people waiting on him, then near deadlines, then tasks that others depend on — which explains why no task list is browsed by hand anymore.

The panel itself is a custom Orca plugin, and each entry is laid out for speed: the decision on the first line, the facts needed below it, then the options, with deeper context left in the PR or task page. A red frame at the top surfaces workers stalled on command permission, which otherwise stay silent. Requests arrive from several directions — review comments tagged N1, N2 so he only picks which to post, and recommendations attached to policy questions — so the exchange with the commander has narrowed mostly to numbers and one-word replies. The reserved connection to a disaster-prevention firm, Rescue-Nau, appears only as the blog's publisher, not as part of the workflow itself.

FAQ
How does he actually respond to the agent's requests?
With a number and a short word, such as "41 OK". He batches answers once several have piled up, and the agent relays them to the workers and records them in Notion.
Where do the items waiting for confirmation appear?
In a panel he built himself as an Orca plugin, in the editor's right sidebar. It reloads whenever the agent's state changes, so new requests show up as soon as the commander raises them.
What kinds of decisions still reach him?
Design choices and production changes with real options, reviews of other people's pull requests, a worker stuck on a policy question, and manual steps only he can do, such as aws sso login.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleNasdaq 100 sheds record $2.3 trillion as chip rout deepens