Background Jobs
Background jobs let Anyy accept substantial work, return a stable job handle immediately, and continue running it in a child session while you use the parent conversation.
Start Background Work
State the intent explicitly:
Run this as a background job: review the uploaded reports, compare their recommendations, and notify me when the comparison is ready.
Anyy uses background mode only when you explicitly request long-running/background work or a completion notification. It does not infer background execution from words such as “download,” “website,” or “research.”
The acceptance response includes a background job ID, a subagent run ID, and a child session ID. Keep the response when you need to inspect or cancel that exact run; those identifiers serve different purposes.
What Happens Next
- Anyy creates a child session with the task and current permitted tool policy.
- The resident runtime records an
agentbackground job. - The parent turn returns without waiting for the child to finish.
- Completion or failure is written back to the parent session inbox.
- Dashboard or the originating supported channel shows the terminal notification.
Background work remains inside the same Profile and survives the foreground conversation moving on. A normal subagent cannot recursively start another background job.
View Background Sessions
Dashboard → Chat separates normal conversations from background sessions. Open the Background list to inspect the child conversation and its tool activity. Completion notices show the job kind, status, and job ID when available.
You can also ask in the parent conversation:
List my background jobs and tell me which are still running.
Cancel or Inspect
Return to the parent conversation and ask:
Show the status and latest history of background job JOB_ID.
Cancel background job JOB_ID and confirm its final status.
Anyy first lists the parent’s child runs to resolve the background job ID. The subagent history and cancel tools take the subagent run ID, not the background job ID, and reject a run belonging to another parent. History is bounded; open the child session in Dashboard for more detail.
Anyy also tracks background process jobs and Cron delivery bridge records. Process log/wait/kill controls apply to process jobs, not Agent children or Cron records. Ask Anyy to identify the job kind before choosing a control.
Cancellation is best effort: a remote operation already accepted by an external service may not be reversible. Review the final status rather than assuming cancellation undid side effects.
If the answer must be summarized in the current turn, ask Anyy to delegate the research instead. Background jobs are for durable work that can finish later.
Limits and Cost
Background work uses a child model run and can call allowed tools, so it consumes provider tokens, tool quotas, time, and external-service cost independently of the foreground chat. You may specify a Role, Workspace, model, label, or timeout when needed. By default a parent can have at most three accepted/running child runs, at one child level. The child’s tool policy is more restricted than the parent’s: memory writes, creating more agents/automations, messaging, and credential access are among the disabled capabilities. Completion delivery belongs to the runtime.
Troubleshooting
| Symptom | Check |
|---|---|
| Anyy performs the work in the foreground | Explicitly say “background job” and request completion notification |
| No terminal notification arrives | Open Dashboard → Chat → Background and inspect the child session |
| Agent child needs user input | The child fails with error class clarification_pending; inspect the question in its session and provide the missing facts when requesting the next run. It is not a successful completion. |
| A child cannot start more background work | Recursive background jobs are intentionally disabled |
| Cost is higher than expected | Review child model, timeout, tool calls, and number of concurrent jobs |