All articles

Product

Copilot or Autopilot: delegate while staying in control

Autonomy modes define what Nectarr can do on its own. Understand approvals, limits, and policy checks before giving the agent more room to act.

Nectarr2 min read
A four-position control dial, lilac shield, and orange key made from matte clay.

Delegating marketing work to an agent raises a practical question: which decisions will it make without you? In Nectarr, the answer depends on the autonomy mode, the action’s risk, and your workspace policy.

Changing modes does not remove budget limits or the permissions needed to use an integration.

Understand the four modes

Observe focuses on read-only analysis. The agent can read and explain, while its actions that change a system are blocked. A step that must be completed by the founder can still be handed over to them.

Suggest allows the agent to prepare drafts. External actions require approval, subject to configured rules for reducing spending exposure.

Copilot also prepares drafts automatically. It asks for approval for publishing and spending actions. This is a useful starting point while you learn how the agent makes proposals.

Autopilot allows more actions within your policy. Sensitive actions still require approval. Automatically launching new paid campaigns depends, among other things, on the relevant policy setting.

A mode does not replace guardrails

Before acting, Nectarr checks a request against applicable rules: permissions, experiment budget, spending pace, and other configured limits.

An action may be allowed, sent for approval, or blocked. These are different outcomes. An approval request means a human decision is needed. A block may indicate a hard limit that approval alone cannot override.

An action that reduces exposure, such as pausing a losing ad, may be allowed automatically when the policy permits it. Review that setting alongside the rules for increasing spend.

Read an approval request carefully

Before approving, inspect the exact deliverable, the destination system, any cost, and the rule that triggered the request. Compare the proposed state with the current state.

For an ad, review the promise and destination. For a budget change, consider the other experiments already running. A reasonable expense on its own can become too much when added to everything else.

Increase autonomy gradually

Start with actions that are easy to review. Watch the proposals, correct product memory where needed, and check outcomes against your connected sources.

Before moving to Autopilot, review connected permissions, spending limits, and the actions that always require approval. Delegate more when you understand the rules and know how to monitor what happens.

Choose autonomy with explicit limits and observable results.

The audit log helps you trace actions that were taken. Keep a regular review habit even as you delegate more work.

Explore Nectarr’s controls