Give coordination a home
The Index thread is the place to coordinate work across threads. Keep your priorities, links to active work, and decisions that span projects there. Start a session in the Index thread when you want to ask what needs attention or delegate work without entering each thread yourself.
Ask the agent which threads to review and what to bring back. It builds the overview from their context, saved results, and session state.
Set the scope
- Open the Index thread.
- In its
context.md, name the threads it covers, your priorities, and how you want work delegated and reported. - Keep a short overview in the thread, with links to the detailed plans and results in each working thread.
- Start a session and ask it to review that scope before proposing the next moves.
This thread coordinates projects/onboarding and projects/website.
Keep priorities and cross-project decisions here.
Keep implementation plans and results in their own threads.
When delegating, give each session a task, an output path, and a
clear stopping condition. Record which session owns each task.Ask for an overview
Review the context, recent results, and Awaiting items in the threads
listed here. Tell me what changed, what is blocked, and which decisions
need me. Save a short overview with links to the supporting files.The agent can discover threads with hai list threads, read their context with hai thread.inspect, and inspect registered sessions. It can stay in the Index thread while reading the others. Reading a thread does not move the coordinating session into it.
Ask it to distinguish saved results from work still in progress. A live session or a recorded status alone does not tell you whether a task is complete.
Delegate and steer the work
Start a Codex session on projects/onboarding to review the proposed
form changes. Have it read the brief and write out/form-review.md.
Ask the existing website session for its current blocker.
Keep a record here of who owns each task and where results will land.Haicue lets the coordinating agent choose a runtime, label, model, and effort when opening a session, subject to that runtime’s support. It can then send instructions or follow-up questions to a specific session. Newly opened sessions retain a link to the session that launched them.
Give the receiving session the relevant context and expected result. Ask it to save its findings and report back to the coordinator. Sessions retain separate conversations, so make the handoff explicit.
See Work with multiple agents for session commands and how to avoid overlapping edits.
Reorganize threads as work changes
Ask the agent in the Index thread to rename threads or move them into a clearer structure while keeping their sessions intact. Haicue’s thread-move command updates the stored thread references and session associations along with the folders, so existing sessions remain connected to the work.
Group the onboarding and website threads under a product category.
Show me the proposed structure first, then use Haicue’s thread-move
command to apply it while preserving the existing sessions.The agent can preview a move plan before applying it. Use that supported operation when reorganizing threads so the folder moves and Haicue’s records stay together.
Let the agent arrange the workspace
The same session can operate other parts of Haicue as the task calls for them: create or update an automation, record an Awaiting item, show findings in Cues, attach a local app, or build a reusable skill.
Set up a weekday review of these threads at 9:00 America/Vancouver.
Have it update the overview and flag decisions that need me.
Show me the automation definition before saving it.This is how the Index thread becomes useful beyond a list of links. The agent can organize the next steps and use Haicue to carry them out. Each feature still has its own setup and controls; a coordination session does not enable add-ons or grant service access by itself.
Return without depending on one session
Before ending the coordinating session, save the priorities, outstanding delegations, session IDs, and result paths in the Index thread. A later session can read that record, inspect the current state, and continue.
The Index thread keeps the overview. The working threads keep the details. Link to a decision or result where it lives so the overview stays short and can be checked.