chat-worker

chat-worker — the user can talk to you, and it must stay cheap

The user is not in a tmux session. They write from the game / desktop app, one-to-one with you. The app tags the message and drops it into your pane:

[@utente -> @scout-2] [CHAT] Come procede il giro delle board?

• Same envelope as inter-agent traffic, but the [CHAT] type and the @utente author make it unambiguous: this is the person you work for.
• There is no tmux session to answer into. jht-tmux-send UTENTE … returns exit 2. [CHAT] ⇒ jht-send. Always.
• Reply to the body, not to the envelope. The user did not type the prefix.
• The delivery tool waits for your current turn to end before typing into your pane, so a [CHAT] never lands mid-thought. When you see one, your turn has just started: answer first, then resume.

How to answer

jht-send 'Sto girando le board EU: sei posizioni nuove stamattina, quattro remote.'

One call. No flags. That closes the turn and the bubble appears in the game.

⏱️ The cost rule — this is the point of this skill

Your reply is one full turn of your model, taken out of the same budget that pays for the work the user is waiting for. A chatty worker is a worker that scouts less, scores less, writes less. So:

1. Answer from what you already have in context. No new query, no new fetch, no new scrape, no file to open "just to be precise". If you do not already know, say what you know and how you will find out — do not go and find out now.
2. One to three sentences. Concrete: numbers, state, what you are on. The user is looking at a comic balloon, not a report.
3. One reply per message, then back to work. Do not close with "anything else?" — an invitation costs another turn, and then another.
4. Batch. If two or three [CHAT] lines piled up while you were mid-turn, answer them all in one jht-send.
5. No --partial. The checkpoint flag exists for a coordinator running a long user-facing operation. If answering you properly would need a long operation, that is the signal that this question is not yours (see below) — not the signal to start one.
6. Never poll. There is no inbox to check. The message is injected into your pane; if there is nothing in your pane, there is nothing to answer. A while true check loop would burn your whole window on "no messages".