HQ: directors and recurring work

HQ gives ongoing work a home. A director has a persistent main conversation, a playbook, routines, and a view of the work it delegates. A staff member is a reusable agent definition that can perform work for a director or start its own session. An agent is a running session of either kind.

Start with a director

Open HQ and create a director. Give it a name and describe the work you want help with. You can start from a library entry or create your own. Choose a supported chat adapter and wait for the main conversation to start successfully.

Describe one concrete outcome first. A director can work with you directly or delegate a bounded task to a worker. Follow the returned report and ask for changes in the same conversation. Creating more workers is optional; the point is to keep responsibilities and results clear.

Give recurring work a routine

A routine wakes a conversation or starts work on a schedule. Set the instruction, timing, and scope, then check its result. A routine that fired has started its work; it has not necessarily finished successfully.

You can pause or change a routine when the work changes. The machine that owns it must be running and have the tools and access the work requires. See tasks and runs for the existing task scheduling model.

Keep instructions in the playbook

A director's playbook holds standing guidance for later work. Save instructions you expect to reuse, then resume the director or start a new chapter so it receives the updated playbook. Check that it follows those instructions in its next turn. Library entries can supply an initial role, playbook, and routines; review those choices when setting up the director.

The notebook and attached notes give you places to keep useful context. An automatically created dashboard is a starting surface, not evidence that a task has been completed.

Stay involved

Review requests and reports as they arrive. Approve, reject, or ask for changes according to the work. Full autonomy is optional, and connecting a tool does not mean every use of it is approved.

Directors use the same connector controls and agent chat foundations as other sessions. Work remains on its owning location.