Setup and recovery

Use the setup or recovery item to resolve the actual blocker. Dismissing a notice does not repair access or resume a paused schedule.

Missing credentials

The item identifies the website, requesting Agent, credential kind, reason, and account-signup option. Open Provide access to select a suitable Vault credential, add one through the embedded write-only form, or approve a separate account with the configured signup email. Reject the request when the access is unnecessary.

The add form starts with the requested kind. You can correct it to a login, API key, or generic secret and include an authenticator setup key for a login.

Durable access is labeled For this task when a Task asked and For this agent when taskless Chat asked. One use is the limited alternative. A successful selection, addition, or signup approval grants the chosen scope and resumes the waiting Task or originating Chats. Rejection and dismissal leave those Chats paused.

See Vault for the complete credential flow.

Expired service authorization

An expired Connector account can pause the work and raise a Log in again request. Complete the provider's consent flow from that item. Successful authorization returns you to the originating surface, clears the related recovery requests, and resumes the waiting work.

Temporary service and network failures remain retryable errors rather than asking for another login. Changing the Agent's assignment does not repair the expired account. See Connectors.

Paused recurrence

A recurring Task or Workflow that is blocked or has a failed current Run receives a Recurring schedule paused item. Its details identify the schedule, current occurrence, blocker, and available failure evidence without requiring a trip to Tasks or Runs.

Resolve invocation cancels that occurrence so recurrence can continue. Stop recurring schedule archives future recurrence while leaving the current occurrence available for review. Dismiss clears only your notice. It does not resume unsafe work.

Use the original question, approval, or Run-failure item when you want to resolve that underlying blocker instead. New setup can also ask you to Set schedule before a recurring job begins. See Schedules.

Execution configuration

If an Agent has a fixed model that Cloud does not offer and no Local Worker is selected, an execution item asks an authorized manager to choose an available configuration.

Choose Choose another to open configuration in Inbox. Choose Auto, another Cloud model, or a supported model from a connected Local Worker, then save there. When a replacement recommendation is available, review it before choosing Use recommended model instead.

A successful configuration updates the Agent and completes the related active requests. Dismissing your copy does not clear another manager's request or make the unsupported model runnable.

Some items have no task behind them. A budget warning or a machine-level alert belongs to the workspace or a worker. Those items still keep their decision context and resolution in the Inbox, with destination links reserved for optional detail.

Repository decisions and recovery stay in the Inbox

A Chat that needs source context can ask its owner for repository access without guessing which codebase to use. The request names the Chat and agent, explains why the conversation paused, and keeps the complete choice in the Inbox. The owner can choose an active workspace repository, create one and finish SSH setup, or decline.

Approval binds that repository to the Chat and resumes it. Declining leaves the Chat without repository context and resumes it with that outcome, so either decision ends the wait.

A task can make the same request when its agent discovers that source context is necessary. Task Machine blocks the Task while sending one Repository needed decision to a human who can update the task and manage repositories.

The decision keeps repository selection or creation in the Inbox, and attaching an active repository resumes only this recovery block. A task that does not need repository context remains valid without one.

A coding task or repository-backed Chat can also fail for an ordinary run reason, or because the repository refused Task Machine's key. When the failure is a confirmed SSH public-key rejection, the Inbox raises a repository access required item instead of a generic failed-run alert or a pasted Git error.

The reminder is scoped to the repository so you fix access once and then continue the affected Task or Chat.

That scope matters when the same repository is used again. Each person who is allowed to change both the task and the repository setup sees only the newest open reminder for that repository, so a later failure replaces an older one instead of stacking duplicates. Another repository keeps its own reminder.

If your permission changes while a reminder is open, its detail explains that an owner or administrator must finish setup instead of showing controls you cannot use.

Opening the item shows which repository blocked the work and keeps the recovery actions together. The public key and provider-specific steps for GitHub, GitLab, Bitbucket, or another Git host appear directly in the Inbox detail. If the key could not be prepared yet, the detail offers Retry key setup first.

Once the public key appears, add it in your Git provider and use Retry Task or Retry Chat from the same detail. A failed checkout instead asks you to verify the saved clone URL and access before retrying.

The item is marked handled only after the retry is scheduled, so a retry that cannot start leaves the reminder open for the next person who can act.

The reminder also clears on its own when access is working again. After a later run gets past repository access successfully, older repository-access reminders for that repository are archived automatically, so the Inbox returns to showing only work that still needs a human fix.

Update a connected computer

When a connected computer needs an update, its Inbox item identifies the machine and available version. Use Update now when offered. Manual installation belongs in CLI setup.