Set up a Project

A Project is a scope: a goal, the repositories that goal is about, and the places Cogno may take events from on its behalf. Its tasks gather on its own page, and the work Cogno runs for it runs in a checkout you nominate. Open Projects from the sidebar. The page is a ledger of that configuration — one card per project showing its name and its goal. It carries no progress bars, percentages, or date chips; progress lives in Tasks and on the project’s own page.

​

Prerequisites

• A workspace you can write content in.
• GitHub connected, if you want to name the repositories a project is about — see GitHub. Without it the repository picker reads Connect GitHub to choose repositories.
• A connected integration, if you want the project to reach one — see Integrations.

​

Create a project

​

Write the project’s goal

The project’s page has a Configuration card on the right. Its Instruction section holds the same sentence the create dialog called the goal — what this project is and how Cogno should act in it, written once. An unwritten one reads Say what this project is and how Cogno should act in it. Select the text to edit it. It saves when you click away; Escape reverts. This is the text the Projects cards show, so a project you describe well is a project you can recognize from the ledger. A card with nothing written reads No description yet. Above it, Owner names the member who owns the project; unset, it reads No owner.

​

Choose what the project may reach

Filter in the Configuration card is the project’s boundary on your workspace’s integrations: Cogno only takes events from what is listed here. Nothing listed means nothing reached — the default is closed, and an unfiltered project reads Nothing yet. Remove a place with the ✕ on its chip (Remove <target>). A project may list up to 500 places per tool.

​

Name the repositories the project is about

⋯ → Edit repositories… in the Configuration card’s header opens Repositories: Which repositories this project is about. A worker environment must hold every required one to run its work. A project may name up to 20. This is what makes a worker environment usable for the project, so narrowing it can strand a checkout somebody is already working in. Cogno refuses that edit and says what it would break — This change strands environments already serving this project, naming what each is missing and who it affects. Select Change anyway to proceed regardless.

​

Choose where the project’s work runs

Which control you see depends on your workspace. See Getting started for connecting a machine in the first place.

​

Set the dates

Dates carries Start and Target. An unset one reads Set date to whoever may set it, and is simply absent for a reader who may not — an empty pill that opens nothing is an invitation you cannot take.

​

Narrow the project’s task list

Under the project’s name is the same search box and Filter the Tasks page carries, scoped to this project. Type into Search title or #123… to search by name, or open Filter for the criteria: There is no Project criteria here — the page is already one project, and the filter cannot take the list outside it. The list opens on Backlog, Ready, In Progress, In Review and Done; Archived and Rejected are left out until you ask for them. Reset in the panel’s header returns to exactly that, and Clear filters at its foot drops every criteria while keeping what you typed in the search box. A filter that matches nothing reads No tasks match this filter — the project still has its tasks.

​

A list too long for one page

A project with hundreds of tasks does not send them all at once. The page opens on the first stretch of the list and fetches the rest as you scroll; the foot of the list says Load more — showing 50 of 240 and loads it on its own as you reach it, or on a click. While a group is still filling, its count reads 12+ rather than a number. Only the last group on the page can be in that state — the ones above it are complete and count exactly. The From Cogno lane is never partial: it is fetched whole, separately, so a proposal is never hiding further down the list.

​

Answer what Cogno proposes

A project’s still-unaccepted tasks gather in a From Cogno lane above the status groups on the project’s page — the same lane Tasks carries for the whole workspace. A task stays there until a person answers it; accepting drops it into its status section below. Two ways to answer:

• From the lane — hover a row for ✓ (Accept suggestion) and ✕ (Dismiss suggestion).
• From the task — open it, and the right rail carries Cogno’s own card. There is no approve button: Pick a status to accept it — choosing a status from the card’s status chip is the acceptance. ✕ dismisses.

Where each proposal came from, and everything else about accepting them, is in Work with Tasks.

​

Delete a project

⋯ → Delete project in the Configuration card’s header. Cogno names what it holds first — This project has N tasks. Deleting it cannot be undone.

​

Reference

​

The Configuration card

The header’s ⋯ menu carries Edit repositories… and Delete project. Any workspace member with content-write permission can edit the card; a reader sees values instead of controls.

​

The Projects card

​

Limits

​

Troubleshooting

For anything not listed here, see Troubleshooting.

​

Related docs

• Work with Tasks — the statuses, the From Cogno lane, and accepting suggestions.
• Concepts — how events, the agent, and workers fit into one loop.
• Integrations — connect the tools a project can reach.
• GitHub — connect the repositories a project is about.
• Instructions — the standing workspace rules Cogno follows everywhere.
• Getting started with Cogno — set up the loop end to end.