Prerequisites
- A Cogno workspace where you can create or edit Tasks.
- For agent work, an Environment connected to the Task’s Project. See Set up a Project.
Open a Task
In a browser, selecting a Task opens a side peek over the current page. Drag its left edge to resize it. Use Expand to full view to open the full Task or Close task panel to return to the list.
A Task bound to another machine shows Runs on <machine> or Runs on
another machine. You can still read and edit the statement from the current
surface.
Understand Cogno-managed work
Cogno can create Tasks from connected events and can keep control while it works on them. These Tasks use an orange treatment.- In desktop List view, Cogno-controlled Ready Tasks sit in a Cogno group inside Ready. Running Cogno work sits in a Cogno group under that person’s tab in In Progress.
- In Board and mobile List, the Task stays in its ordinary status position and keeps the orange treatment.
- Top-level Tasks keep the source they came from. Show the Source column or read the inline from <source> mark.
suggested:true to see Tasks
whose proposed status remains unresolved. See
Task statuses.
Create a Task
Create and start from Desktop
Select Work and write in What do you want to work on? Choose a Project, base branch, and model, then select Create or press Enter. Cogno creates a Ready Task, opens it, and sends the prompt as the first turn. The person chip beside the Project (Who works on this) names whose machine runs the work. It starts as you. Choose someone else and Create assigns the Task to them and queues a run for their machine instead of opening it here: the run starts at once when they have a folder connected for the Project, and otherwise the Task waits under their tab in In Progress until they connect one. The attachment, model, and base branch controls belong to your own machine, so they step out of the composer for someone else. The + on a person’s tab in In Progress opens this composer preset to that person. You can attach or paste files before creating. One message accepts up to 20 files; a local agent refuses a file over 25 MB. The send waits until every attachment finishes loading. The base branch defaults to the repository default. A direct Environment has no Git branch or automatic pull request. A named local-only branch also shows no automatic PR.Choose an exit from the full form
The full form’s How to proceed panel combines assignee, Environment, and the next action:1
Describe the work
Add a title and description. The editor accepts rich text, mentions,
tables, and images.
2
Choose who and where
The Environment starts at Automatic. Open it to use Automatic
routing or choose one registered Environment.
3
Choose what happens next
- Watch it get built creates the Task and starts implementation.
- Plan it first creates the Task and starts a planning turn.
- Later creates the Task in Backlog without a run.
- Create creates the Task in Ready without a run.
Start and follow work
There is no separate run button. In the desktop app, send a message in the Task conversation. The first message claims an Environment and moves the Task to In Progress. Later messages continue the same Task session. The composer reads Message the agent… for work this surface can send directly. For work owned by another machine it reads Send to Cogno… and queues the turn there. While work starts, the conversation shows Starting…. During the turn it shows Running…, and the send control becomes Stop. You can send another message to steer the active turn. Stop the turn before changing its model or Plan mode. Attach, drop, or paste files into the composer. Images appear as thumbnails that open full size. Failed uploads block the message until you remove them.Start work for a person from the list
Drag a Task onto a person’s tab in In Progress, or onto the rows under the open tab. The Task is assigned to that person and a run is queued for their machine. On a Project page, dropping a Task onto your own name at the top of the sidebar does the same for you.- With a folder connected for the Project, the run starts right away.
- Without one, the row shows a hollow branch mark whose tooltip reads Starts when <name> connects a folder. The run starts on its own the moment they connect one.
- A Task that already runs in an environment stays with its owner. While you hold it over another person, the lane shows Fixed to <name>‘s environment, and releasing it changes nothing.
- While a run is executing, the row’s mark spins for everyone in the workspace, not only on the machine doing the work.
Move through the lifecycle
Change status from the Task, its row menu, or by dragging in List or Board.- Moving into In Progress without starting work is refused with Send a message in the Task to start work. Dropping the Task on a person’s tab in In Progress is the way to start work from the list; see Start work for a person from the list.
- Moving out of In Progress during a live run opens Stop the running agent and move? Select Stop and move to retain partial results and end the run.
- A completed or failed run can propose Backlog, Ready, or In Review. It cannot close its own Task as Done.
- Select Done when the work is complete.
Edit, archive, or delete
The Task statement contains Status, tags, dates, assignees, Project, preview, and actions. Descriptions support rich text, collaborative editing, and version history. Archive removes a Task from active views and is reversible. Delete permanently removes the Task, sub-Tasks, comments, attachments, and history. On a machine that ran it, deletion also removes the local conversation and working copy, including uncommitted changes.Troubleshooting
For other failures, see Troubleshooting.