Proposals

A proposal asks whether a suggested change should become part of your Workspace. Read its scope and rationale, inspect the candidate, and decide in Inbox. Different proposals create work, add capabilities, or revise something you already use.

Tasks

A Task proposal opens the complete editor in its decision modal. Adjust the brief, acceptance criteria, scope, assignments, timing, and labels before approving, according to your permissions.

Choosing an assignee while reviewing does not start work. Approval saves the final proposal and applies the ordinary assignment, planning, and execution behavior. If you can approve but cannot change assignments, the existing assignment choices remain unchanged.

Inbox history keeps the reviewed proposal and outcome rather than replacing them with the Task's later contents.

Agents and Teams

Review a proposed Agent's role and configuration before adding it to the workforce. For a Team, check the responsibility and routing arrangement rather than treating the Team as another executing Agent.

An update to an existing Agent names the same Agent and shows the changed values, including instruction differences and Skill additions or removals. Approval updates that Agent. It does not create another one. Rejection leaves the accepted configuration unchanged.

Projects, Goals, and labels

Review how a proposed Project or Goal fits the work you intend to delegate. These proposals establish organization and context, not proof that the resulting work is complete.

A Project-label proposal shows its Project, name, color, description, proposer, and rationale. Check the intended meaning before activating another label that people will use to classify Tasks.

Chats

A proposed child Chat shows its opening message, target Agent, and the proposer's rationale. Read the actual question or direction before approving another conversation.

Skills and Connectors

A Skill proposal adds reusable expertise. Review its instructions and purpose separately from the service access an Agent may need. Marketplace Skill updates have their own review flow according to the Workspace's update policy. See Skills.

A Connector proposal shows the connection and its intended use. Approve and configure opens its prefilled setup in the same flow so you can finish authentication and verification. Rejecting it records your reason without making that connection available.

Workflows and Playbooks

Inspect a proposed Workflow's graph, assignments, decisions, and outputs before approving a process that can run repeatedly. A revision includes the accepted and candidate graphs so you can compare the whole change.

A Playbook groups its coordinated setup under one installation decision. After approval, finish the connection and timing requests it raises in Inbox before expecting the work to run. See Playbooks and Setup and recovery.

Changes to existing configuration

Agents can propose revisions to Agents, Connectors, Teams, Projects, Goals, Workflows, and installed Playbooks. Compare the accepted setup with the candidate, including changes to access or responsibility.

A Playbook update groups its component comparisons under one decision rather than asking you to approve the same coordinated change several times. Workflow creation and Workflow updates have separate approval gates.

Approval rechecks that the reviewed base and referenced resources are still valid. A stale proposal does not overwrite newer accepted configuration. Rejection or retraction leaves the accepted setup untouched.

Browse a proposal backlog

The relevant feature's Proposed tab lets you browse pending suggestions of that kind. Your access determines which proposals and actions are available. Inbox remains the place to work through the decisions routed to you without switching surfaces.

For questions, Work Spec approval, completion review, and access decisions, continue with Questions and approvals.