Missions

Start and follow a conversation

Choose an agent in Chat, enter a concrete request and send it. The mission records assistant output, tool activity and its completion state. Use the mission view to inspect activity and errors when a result is missing or unexpected.

From a terminal:

timon spawn project.writer "Describe the current project."

The response contains a mission_id. Use that ID with timon status, timon send or timon wait. A follow-up to a running mission steers the existing work; the mission history remains available for inspection.

timon status MISSION_ID
timon send MISSION_ID "Focus on the installation instructions."
timon wait MISSION_ID --timeout=120

To interrupt work deliberately, use the mission's stop control or timon kill MISSION_ID. Interruption does not mean the requested work was completed: check files and task status before retrying.

When a subscription quota is exhausted

Timon records backend cooldowns and consults the fallback plan before dispatching more work. Task-specific choices take precedence; a series can define different fallbacks for its coordinator and task types. An explicit refusal to fall back remains a refusal.

Eligible pending work can move to another available backend. Running tasks are not all killed just because a different task hit its quota. Tasks blocked for a business reason are not automatically cleared as quota failures.

The model catalogue and quota reset times come from the active backend. A missing usage probe is unknown usage, not a zero-percent gauge. A provider that does not report a reset time cannot give Timon an exact reopening promise.