> ## Documentation Index > Fetch the complete documentation index at: https://docs.murmur.dev/llms.txt > Use this file to discover all available pages before exploring further. # murmur autopilot-timeout CLI command > Bound how long a running Murmur agent keeps acting on CI results, PR comments, and merge conflicts on its own before it turns those settings off and waits for a human. Sets how long an [agent](/concepts/agents) acts on [events](/concepts/events) by itself — CI results, pull-request comments and reviews, and merge conflicts in its repos. The window is measured from the last human interaction, or from the moment autopilot was last turned back on, whichever is later. Before either, it runs from the moment the agent started. Only a person restarts the clock: a follow-up you send, a PR comment you write, a review you leave. Bot comments, CI results, and the agent's own retries do not. When the window lapses, the agent turns all three settings off and leaves them off. A later human message moves the clock but does not turn them back on — turning any of them back on is explicit, and grants a fresh full window from that moment. Nothing is terminated and no running turn is interrupted: the agent stays reachable, and still responds to anything you send it directly. ## Synopsis ```bash theme={null} murmur autopilot-timeout [flags] [slug] ``` On a VM the slug may be omitted, which targets the calling agent itself. ## Arguments | Name | Type | Required | Description | | ------------- | ------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | `slug` | string | on laptop | The [agent](/concepts/agents)'s slug. Optional on VMs (defaults to self). | | `duration` | string | yes | A Go duration between `1m` and `8760h` (e.g. `72h`), or `0` for no limit. Empty is rejected here — the agent resolved its default when it spawned. | | `--json` | bool | no | Print the `SetAutopilotTimeoutResponse` as JSON (`{}` on success). | | `--workspace` | string | no | [Workspace](/concepts/workspaces) name. Overrides the value from `murmur.yaml`. | The new value takes effect on the agent's next event, and applies to the window already running — it is not a fresh window. ## Output ``` autopilot timeout set to 72h for fix-auth ``` The timeout in force and the moment it expires are both in [`murmur status --json`](/cli/status), as `autopilotTimeout` and `autopilotDeadline`, and on the agent's dashboard page. `autopilotDeadline` is unset when no timeout is in force, and once the settings are already off. ## Examples ### Bound an agent to three days of autonomy ```bash theme={null} murmur autopilot-timeout fix-auth 72h ``` ``` autopilot timeout set to 72h for fix-auth ``` If nobody messages `fix-auth`, comments on its PR, or reviews it for 72 hours, the agent stops reacting to CI results and PR comments, sets every repo's conflict resolution to `NONE`, and waits. ### Let an agent run unattended indefinitely ```bash theme={null} murmur autopilot-timeout fix-auth 0 ``` ``` autopilot timeout cleared (no limit) for fix-auth ``` ### Bound the calling agent from its own VM ```bash theme={null} murmur autopilot-timeout 24h ``` ``` autopilot timeout set to 24h for self ``` ### Read the deadline back ```bash theme={null} murmur status fix-auth --json | jq '{autopilotTimeout, autopilotDeadline}' ``` ```json theme={null} { "autopilotTimeout": "72h", "autopilotDeadline": "2026-03-04T11:20:31Z" } ``` ## Turning autopilot back on The three settings the timeout governs are turned back on separately, and turning any one of them back on starts a fresh window: * CI results and PR comments are [suppressed event classes](/concepts/events) — toggle them on the agent's dashboard page. * Merge-conflict resolution is per repo: [`murmur queue conflict-resolution `](/cli/queue-conflict-resolution). ## Errors | Code | Meaning | What to do | | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | | `invalid autopilot_timeout` | The duration is not a Go duration. | Pass a duration like `72h` or `90m`, or `0` for no limit. | | `autopilot_timeout must be between 1m0s and 8760h0m0s` | The duration is outside the accepted bounds. | Pass a value of at least one minute and at most one year. | | `usage: murmur autopilot-timeout …` | No duration was given, or the slug was omitted off a VM. The command prints its usage and stops before calling the server. | Pass ` ` from a laptop, or `` alone on a VM. | | `NOT_FOUND` | No agent with that slug exists. | Check the slug spelling. Use [`murmur ls`](/cli/ls) to see running agents. | | `PERMISSION_DENIED` | You lack `agent.edit` on this agent. | Ask a tenant admin for the permission — see [Permission reference](/security/permission-reference). | | `UNAUTHENTICATED` | Identity token is missing or expired. | Run `murmur auth` or check your `murmur.local.yaml` configuration. | ## Related * [`murmur spawn`](/cli/spawn) — set the initial value with `--autopilot-timeout` * [`murmur status`](/cli/status) — read the timeout and deadline in force * [`murmur queue conflict-resolution`](/cli/queue-conflict-resolution) — turn merge-conflict resolution back on for a repo * [`murmur on-idle`](/cli/on-idle) — what the agent does when it goes idle, a separate clock * [Events](/concepts/events) — the event classes autopilot governs * [workspace](/catalog/workspace) — `default_autopilot_timeout` for every agent spawned in a workspace