Skip to main content
An agent runs a Task in an Environment on a connected machine. The Task keeps the conversation, files, running state, and delivery together while the agent works.

Prerequisites

  • A Task you can edit.
  • An Environment connected to the Task’s Project.
  • An online machine for immediate work. Work remains queued when its selected machine is offline.
  • For automatic GitHub delivery, a Git repository and a connected GitHub App.

Start work

There is no separate run button. Only one run can be active for a Task. Dragging a Task into In Progress does not start work; Cogno asks you to send a message instead.

Choose the Environment

The Task creation form places an Environment control beside the assignee. Automatic uses Automatic routing to select from the Task assignee and available machines. You can also select a registered Environment directly. A Task that has already run keeps its Environment, machine, and directory for later turns. When the machine differs from the current one, the Task identifies where it runs.

Plan at creation and choose a model

Use Plan it first while creating a Task to start with a planning run. The model menu reads models from the selected Engine. Default model follows that Engine’s default. Choosing a named model pins it for the Task. If discovery fails, select Refresh models; Cogno does not invent a fallback model. Model selection stays fixed while a turn is active. Stop the turn before changing it.

Follow the run

While a turn runs, select Stop or press Escape to interrupt it. Pressing Enter on another message adds it to a queue above the composer; the queued messages are sent together as the next turn as soon as the current one ends, including after a Stop. Press ⌘Enter to send now instead: the composer text first, then the queued messages oldest first, all into the running turn. Each queued row has its own send-now, edit, and remove controls. An agent can delegate bounded work to a sub-agent. Open the Agent tool row to read that sub-agent’s nested messages, tool calls, result, tokens, and duration. The Running file-panel segment lists background shells, watchers, or servers only while they remain active.

Review the result

Read the agent’s result in the Task conversation and inspect Changes. A Git Environment with automatic delivery can push a branch and open a pull request. A local-only branch or direct Environment has no automatic pull request. A completed run can propose Backlog, Ready, or In Review. Applying that proposal releases Cogno control. A failed or stopped run leaves a Cogno-controlled Task in In Progress. The agent cannot select Done for its own work. Review the result and move the Task when you decide it is complete.

Run states

pending, claimed, and running are live states. Completed, failed, and cancelled are terminal run states; they do not close the Task.

Troubleshooting

For other failures, see Troubleshooting.