Let sessions hand tasks to each other

Say one session builds a website and another watches the server. The website session needs to know what is on the server: no need to carry text by hand, Hedoq passes the question and brings the answer back.

Step by step

1. In the session that will ask, click ⚡ in the message field.
2. Pick a command:
   • “See what another session is doing”: it sends a short summary;
   • “Give a task to another session”: it does the task and replies;
   • “Show another session screen”: this session reads it and tells you what is there;
   • “Break the link with a session”: the sessions stop messaging each other.
3. Pick the session from the list.
4. The ready text goes into the field without sending. Add your task and press Enter.
5. The answer arrives in this session once, as a message marked [Hedoq].

Good to know

• Sessions only message each other when you tell them to. They never start on their own.
• Until a session answers the previous task, a second one will not be sent to it.
• A sleeping session wakes up when a task arrives.
• Links last until Hedoq restarts.
• If the field shows something like /hedoq-send, that is expected: it is a short call, and Hedoq passes the full text to the agent itself.

For advanced users

Agents inside Hedoq know the hedoq command. You can ask an agent to use it in plain words:

• hedoq list: all tabs and their state;
• hedoq link <tab>, hedoq send <tab> "<text>", hedoq read <tab>, hedoq unlink <tab>;
• hedoq spawn <name> "<task>": a new Claude session in its own project copy, linked and given the task. This is how “Split the task into parts” works.

The agent’s helpers

That is something else. Claude Code can start helpers (subagents) inside its own session. The feed shows them as “Helpers: N of M working”. They do not get their own rows in the sidebar.

See also: model council, parallel sessions.