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. Keep it when you may need to ask about that exact run.
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.
The terminal notice does not silently start another parent model run. On the next parent turn, Anyy projects up to five pending completion/failure updates into that turn's model context, then marks those updates delivered after the prompt binding is durable. If more than five are waiting, later turns can receive the remainder.
This lets the next answer use the child result without copying it manually, while keeping the child transcript in its own Background session.
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
Ask Anyy to inspect or cancel the job by its ID. The model-visible subagent controls can list, inspect history, and cancel child runs within the parent session's scope.
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; Anyy cannot grant the child tools the parent does not have.
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 |
| Job is blocked for approval | Complete or deny the pending approval; unattended work does not bypass policy |
| 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 |