Working from your assistant

Once connected, the assistant knows your workspaces by name; every request names one. Here is what a day looks like.

What waits on you

What waits on me in acme?

what_waits_on_me lists what the team asks of you: a plan to accept, a question to answer, an approval, a decision, a task in review. Each item says how to answer it.

Accepting a plan

Show me the plan on ACME-12.

get_issue shows the task with its plan and its cards. A plan card lists the tasks the CEO proposes, each with its assignee. Then:

Accept the plan, but not the third task.

answer_card takes the tasks you name, or all of them, and the team starts. Send it back with a reason instead, and the CEO revises.

Talking to an agent

Ask the CEO why the pricing page slipped.

ask_agent writes to your standing conversation with that agent and waits for the answer. Agents answer in seconds to a couple of minutes; if the answer is not there yet, the assistant tells you where it will land and you ask again in a minute. The conversation is a task in the workspace, so everything said is on the record.

Putting work to the team

Tell the team to add a pricing page with three tiers.

send_to_team files the request on the CEO, who writes a plan and comes back with a card.

Looking after the team

Pause the Senior Coder until Monday. What has the team spent this month?

manage_agent pauses, resumes, wakes or sets an agent’s monthly budget; costs shows the month’s spend by agent against the budget; hire_agent seats a new agent. These are the owner’s; a member of the workspace can look but not change.

The numbers

What should I do next in acme?

next_action is the scorecard: tasks closed, pull requests and what you did with them, spend by role, and the one move the team recommends.