Features Decisions

Your agent asks, then keeps working.

When a choice is yours, the agent asks it in Beck with the default it's going with, why it matters and the tasks it affects. You answer when you get to it, from your desk or your phone.

Waiting on you, next to the agent's task list. Three questions arrive, each with a default. The costly one sorts to the top. A blocking one holds the task it affects, and the agent moves to another task. You answer it differently from the default: the task is unblocked and marked until the agent hears your answer on its next call, then it goes back. You keep the default on the costly one. One question stays open, its default in use.

Waiting on you

Answer from your phone.

Every open question across your workspaces, costly first. Keep the default in one tap, or say what the agent should do instead. It hears your answer on its next call.

The agent asks whether to keep sessions in the auth provider or its own database, and keeps writing code with the default. The question appears on the Waiting on you page on a phone. Someone taps Keep default. When the agent finishes its task, Beck tells it the default was kept.

How a question works.

  • Every question has a default.

    The agent never waits on a bare question. ask_decision names what it will do, and it does that until you say otherwise.

  • Costly goes first.

    Questions whose default would be expensive to undo are marked costly to reverse, and sort to the top of Waiting on you.

  • Blocking, when it has to be.

    A blocking question holds the tasks it affects, with the reason on each. The agent works elsewhere, and your answer unblocks them.

  • Answers reach the agent.

    It hears them on its next start_task, finish_task or recommend_task. Until then, the task says your answer hasn’t been picked up.

  • Affects, named.

    Each question lists the tasks it touches, so you can see what a different answer would change.

  • Changed your mind late?

    If the task is already done, the agent adds a follow-up task instead of reopening finished work.

Where it sits in the loop

Decisions are the Ask step. The run doesn’t stop for them, and each answer stays on record with the tasks it affected.

  1. 01PlanThe agent proposes the breakdown in your repo.
  2. 02Recordrecord_plan puts it in Beck as a document, epics and tasks.
  3. 03RunEach session shows up on Now while it works.
  4. 04AskQuestions come with a default, and the work goes on.
  5. 05ReviewYou accept the work, or send it back with a reason.
How the loop goes with an agent

Your agent asks and keeps working.

See plans

Free includes 50 AI credits. Recorded plans, runs and decisions use none.