Skip to main content
Tasks is where the work Cogno picks up becomes visible and movable. A task is the core unit of work — a title, description, status, assignees, due date, and tags. You rarely create tasks by hand: Cogno proposes most of them from your events, works on them, and suggests where each one should land. Tasks is the window where you glance at those suggestions, accept or dismiss them, and review what gets delivered. Open Tasks — it’s the workspace’s home screen. From there you can switch how the same tasks are laid out, filter them down, and save a filter you use often.

​
The five statuses

Every task sits in one of five visible statuses, matching the GitHub-style workflow. New tasks you create start in Ready. Two more statuses stay hidden from day-to-day views: Archived (removed from active views, not deleted) and Rejected (dismissed AI suggestions). They don’t appear on the board unless you enable them in the board’s status filter, and Rejected is never offered in status dropdowns. The two main views order the statuses differently, each for its own reading:
The old Active and Proposed statuses are gone — existing tasks were migrated automatically (Active work moved into the new statuses based on its real state; Proposed tasks became suggestions). Saved views and filters written in the old vocabulary keep working: active resolves to in_progress, proposed to backlog, and so on.

​
The Suggested lane

Every status section carries a Suggested lane beneath its main rows — the tasks Cogno recommends for that status, each with a short reason on the right side of the row. A task in the lane is a recommendation, not a decision; the main rows above it are the tasks you (or your team) have confirmed. Hover a suggested row to act on it:
  • ✓ Accept — keep this status and move the task into the main lane.
  • ✕ Dismiss — reject the suggestion; the task returns to where it came from.
When a burst of suggestions arrives, the lane caps its height and offers Show all / Show less so it never shoves the next section off-screen. The lane is how Cogno’s own work flows through your board:
  • New tasks from events (Slack messages, meetings, GitHub activity) appear in In Progress → Suggested while Cogno immediately starts working on them — the live processing feed sits at the top of that lane.
  • When a run finishes, the agent proposes where the task should land — In Review with a PR, Ready when it needs your input, Backlog, or Done — and the task moves to that status’s Suggested lane with the reason attached.
  • The daily loop adds housekeeping suggestions: tasks that sat untouched in Ready or In Review are nudged toward Backlog (a soft 「そろそろ動かしませんか？」 card with Backlog に戻す / そのままにする), and tasks whose pull requests are all merged get a Done proposal with a reason like PR #1234 merged & deployed.
Accepting and dismissing isn’t just tidying — every resolution teaches Cogno what to suggest next time.

​
Create Work

Select New Task to open the creation form. The description field is the same full editor as the task page: slash commands, @mentions, Markdown paste, tables, and images all work while drafting. There is no status picker. Instead, the How to proceed panel on the right decides both who is responsible and how the work starts:
1

Write the Work

Give it a title and describe it in the editor — type / for blocks, @ to mention a teammate, or drop an image straight in.
2

Choose who runs it

The assignee chip defaults to you. Next to it, pick the worker environment — Automatic routes to an available worker, or choose a specific machine. Picking someone else’s worker runs the work there while keeping them accountable as assignee.
3

Pick an exit

  • Watch it get built — create the task and immediately kick off a run.
  • Plan it first — create the task and run a plan-only pass that writes the plan into the description.
  • Later — create straight into Backlog, no run.
  • The quiet Create link at the bottom creates into Ready with no run.
Every exit except Later lands the new Work in Ready — the runs kicked off by Watch it get built and Plan it first then carry it through In Progress on their own.

​
Images in descriptions

Task descriptions (and the creation form) accept images directly:
  • Drag & drop — while you drag, an indicator line tracks where the image will land between blocks; drop to place it there.
  • Paste — an image on your clipboard pastes at the caret.
  • Uploading — each image shows an inline placeholder with the filename, a progress bar, and a × to cancel. Multiple files insert in order as consecutive blocks. A failed upload flips the placeholder to an inline upload failed state you can dismiss.
Accepted formats: PNG, JPEG, GIF, and WebP.

​
Action cards

The panel on the right of a task shows one card at a time — the next step for the task in its current status. The agent writes the card when it delivers; Cogno’s daily loop writes housekeeping cards. Every card carries:
  • A short reason line — → 提案: <status> — <reason>, why the agent suggests that landing spot, placed so you read why before choosing.
  • キャンセル… (Cancel) — dismisses the suggestion. A one-click reason picker opens first — Not needed, Too early, Wrong direction, Duplicate, or a free-text reason — and the reason improves future suggestions.
  • 質問する (Ask a question) — opens an inline input; your question goes to the running (or most recent) agent session, and the answer arrives as the next card.
The primary buttons depend on the suggested status:
Merging is always yours. Cogno proposes Done when it detects a merged and deployed PR, but it never merges a pull request or confirms Done on its own.

​
Move a task to In Progress

In Progress only ever holds queued or running work, so moving a task there by hand (dragging on the board, or picking the status) opens How should this move forward? — pick how the work actually starts:
  • Run with a worker — pick where to run (Pick where to run, or automatic routing); the chosen machine picks the task up from the queue.
  • Open in terminal — resume the task’s saved session in your own terminal (Resume in Claude CLI / Resume in Codex CLI, or Copy command on the web). The session is tracked, so the task stays a truthful In Progress.
  • Cancel keeps the task where it was.
A tracked terminal session shows as In progress in a manual session on the task. When you’re done, select Finish and deliver to close the session and deliver, or Discard to stop tracking it. After a finished session, Cogno offers to reflect what happened into the description — Reflect it or Not now. Dragging a task out of In Progress while an agent is running asks first: Stop the running agent and move? Partial results are kept, and the stop is recorded as a learning signal.

​
The four views

The same set of tasks can be laid out four ways. Switch between them from the view selector in the header. Your chosen view is remembered per workspace, so Tasks reopens where you left it. You can also deep-link a view: ?layout=calendar or ?layout=gantt opens that layout directly. On the Board, a second control groups columns by Status, User, or Project. Drag a card to a new column to update it, or use + New task at the foot of a column to add one there.

​
Filter with the Query bar

The Query bar above the task list filters and searches the current view. It takes a GitHub-style query: whitespace-separated key:value tokens, plus free text that matches the task title (or a task number like #123). Comma-separated values inside one token are OR’d together — status:backlog,ready matches either. When you open Tasks, the default filter shows the four open statuses — status:backlog,ready,in_progress,in_review. Your filter is remembered per workspace and restored the next time you open the page.

​
Query tokens

You don’t have to type tokens by hand — the Query bar builds them as you pick statuses, tags, assignees, and dates. Typing is just the fast path.

​
Save a view

When a filter earns its keep, save it as a Saved View — a named, reusable filter that appears in your sidebar.
1

Build the filter

Use the Query bar to filter the list down to what you want. Once the filter differs from the default, a save affordance appears in the header.
2

Select Save View

Select Save View. In the dialog, give it a View name and choose a scope — Private (only you) or Shared (everyone in the workspace).
3

Select Save

Select Save. The view opens and is now selectable from the sidebar.
When you’ve opened a Saved View and changed its filter, the header offers Save to write the change back into the view, Save as new view to branch it, and Reset to return to the view’s saved query.
Only the person who created a Saved View can save changes back into it. Anyone can open a shared view and use Save as new view to make their own copy.

​
The task detail

Select a task to open the Task detail panel. From there you edit the task’s title and description, set its Status, assignee and collaborators, Start and Due dates, Project, and tags. Descriptions are versioned — open Description history to see saved versions and Restore an earlier one. Versions appear after AI or human edits change the description. The right rail of the task detail is where the action cards appear — the agent’s delivered work and its next-step suggestions live there, alongside the run panel while an agent is working.

​
Reference

​
Task fields

​
View & filter behavior

  • Concepts — how suggested tasks fit the events → agent → execution loop.
  • Instructions — standing rules Cogno follows when it triages and delivers.
  • Memory — the workspace context the agent reads before it proposes work.
  • Getting started with Cogno — set up the loop end to end.