Projects
Organize related issues with projects and give them a shared goal, plan, and execution context.
Projects organize work that takes multiple issues to finish — a product launch, a migration, or a feature delivered in stages.
Work that a single issue can describe does not need a project. Projects fit a group of work that shares a goal, needs its progress tracked together, or needs shared repositories and working directories.
Parts of a project
| Part | Purpose |
|---|---|
| Name, icon, and description | Goal, scope, and long-lived requirements; the description enters the execution context of agents working inside the project. |
| Status | planned, in_progress, paused, completed, or cancelled. |
| Priority | urgent, high, medium, low, or none. |
| Lead | A member or an agent — who coordinates the project. |
| Access | The entire workspace, or only the project's members. See Private projects. |
| Start and target dates | The project's planned time range. |
| Issues and progress | The work in the project and how much of it is finished. |
| Resources | Linked GitHub repositories or local directories on specific computers. |
| Workflow | The steps its issues follow and who takes over at each step. |
Browse projects
Open All projects and use the display menu to choose Table or Board. Both layouts support search and filters for status, priority, and lead. Group by status, priority, lead, or folder; the table can also stay ungrouped. On the board, dragging a project to another column changes that field.
The table can show start date, due date, progress, and last activity. Sort by those fields, name, status, priority, or creation time. Layout, grouping, sorting, visible columns, and filters are saved per user and workspace across devices; search text is not saved.
Projects and issues
A project can contain any number of issues; an issue belongs to at most one project. Create issues directly inside the project, or pick or change the project from the issue's properties.
Project progress is computed automatically from linked issues:
progress = issues whose status is in the done or closed category ÷ all issues in the projectAmong the built-in statuses that means done and cancelled; custom statuses in those two categories count as well. cancelled means that work has been closed out of the project's scope, so it counts toward progress.
Project status and issue status are independent: finishing every issue does not set the project to completed, and changing the project's status does not bulk-change its issues.
- Status
- Lead
- You
- Progress
- 2/4 · 50%
- OPS-41Pick the event theme and dates
- OPS-42Write the event announcement post
- OPS-43List the prizes for the draw
- OPS-44Book a partner influencer
Run the anniversary online event by October 31: the announcement post, the prize draw and partner promotion. Keep the brand voice friendly; budget stays within the approved amount.
Used as project context for agents, applied to every run in this project.
Project description and execution context
When an agent runs an issue inside a project, the project's name and description are added to that run's context. Put what every related run needs to know in the description — the goal, technical boundaries, delivery conventions — and keep requirements for a single issue in that issue.
Add resources
Project resources tell agents which code and working directories to use:
- GitHub repositories: provide a repo the runtime can check out, with an optional ref.
- Local directories: let the runtime on a specific computer use an existing directory; the agent either edits it directly or works in an isolated git worktree of it.
See Project resources for how to choose and for the safety boundaries.
Choose a workflow
Choose the project’s Workflow to set its board columns and who takes over at each step. For example, development can go to one agent, review to another, and acceptance to a team member. Projects without another choice use Default: every status is available and nothing is handed off automatically. See Workflows for setup and switching an existing project.
Project lead
The lead can be a member or an agent; a member who is the lead can also switch the project’s workflow. Making someone the lead does not assign issues to them or start any work. To hand a step to the lead, set that step's handler to Project lead in the workflow.
Private projects
A project's Access is either Entire workspace or Project members only. A private project, with its issues, comments, and attachments, is visible only to the people on its member list. For everyone else it does not appear in lists or search, and a link to it opens as not found.
Who can see a private project
- People on the member list, and nobody else. A workspace role opens nothing: an
owneroradminwho is not on the list cannot see the project. They are added to the list like anyone else, and can be removed from it. - Agents follow the people they work for. An agent run sees a private project only when both the person who triggered the run and the agent's owner are on the list. An issue in a private project can only be assigned to an agent whose owner is on the list.
- A member who leaves the workspace leaves every private project in it.
If you are an owner or admin and a private project no longer shows up for you, you are not on its member list. Ask the member who manages its access to add you; the workspace owner can also join it from settings (see Workspace owner recovery).
Who manages the member list
Managing access means adding and removing members, changing the project lead, and switching the project back to the entire workspace. These people can do it:
ownerandadminmembers who are on the list.- One member the project names as its access manager, marked Manages access in the Access dialog: the lead, when the lead is a person on the list; otherwise the creator, when on the list; otherwise the member who has been on the list the longest.
The lead of a private project can be a member, an agent, or nobody, as on any project. The access manager is not stored but worked out from the lead, the creator, and the list each time, so it moves when the lead changes or someone leaves. Naming a person as lead adds them to the list; to remove the current lead from the list, change the lead first. Other members can see the list but cannot change it. Agents cannot change any project's access.
Create a private project or make a project private
- New project: in the create dialog, open Access, choose Project members only, and add members. You are always on the list, and so is a person you name as lead.
- Existing project: click Access in the project's properties and choose Project members only. Making a workspace-visible project private takes an
owneroradmin; they are added to the list, along with the lead if the lead is a person. - CLI: pass
--visibility privatetoproject createorproject update, with--member(a name, email, or user ID; repeatable) for the initial list. Manage the list afterwards withproject member list|add|remove.
multica project create --title "Pricing revamp" --visibility private --member alice@example.com --member Bob
multica project update <project-id> --visibility private --member alice@example.com
multica project member add <project-id> carol@example.comSwitching a private project back to Entire workspace makes the project and its issues, comments, and attachments visible to every workspace member. The app asks for confirmation first; multica project update --visibility workspace applies the change immediately.
If your workspace plan restricts private projects, existing private projects keep their visibility and member lists. The restriction blocks creating a private project, making a project private, and adding people to a private project, including by naming a new member as lead. Members with permission can still edit project details, remove members, switch access to Entire workspace, and archive or delete the project. The workspace owner can still join through Workspace owner recovery.
Workspace owner recovery
A private project may have no owner or admin on its list, or no members left at all. The workspace owner can step in from Settings → General → Private projects, a section only owners see (admins do not). It lists every private project with its name and members, and nothing else: issues, comments, and attachments stay hidden until you join.
Click Join and confirm to add yourself to the member list. You appear in the list like any member, its existing members get an inbox notification, and as an owner on the list you can manage its access. Joining does not change the lead. A project whose members have all left is recovered the same way: join it, then manage or delete it from the project page.
Folders
Folders group related projects, such as everything for one launch or one team, so the sidebar's Projects section stays short. Folders are shared: every member sees the same folders, and any member can create, rename, or delete one and move projects in and out of it. A project is in at most one folder, and folders do not nest. A folder only organizes projects; it does not change who can see them.
- Create a folder: click + on the sidebar's Projects section and choose New folder, or choose Move to folder → New folder… in a project's menu to create one with that project in it.
- Move a project: choose Move to folder in the project's menu, or drag the project onto a folder in the sidebar, or out of it. When creating a project, pick its folder in the create dialog; + on a folder row creates a project in that folder.
- Rename or delete a folder: right-click it in the sidebar. Deleting a folder moves its projects back to the top level; nothing else changes.
Which folders are open in your sidebar, and the order of folders and projects, are personal and do not affect other members. The Projects section's filters apply inside folders: a folder whose projects are all filtered out is hidden, while an empty folder stays visible so you can fill it. On All projects, group by Folder to see each folder's projects together; on the board, dragging a project to another column moves it to that folder.
Pin to the sidebar
A pinned project appears in your sidebar. Pinning is a personal preference and does not affect other members.
In the Projects section settings, Default icons only replaces custom project icons with the default project icon in that section. It is off by default and does not change the projects themselves.
Archive and restore
Choose Archive project in the project's menu, or Archive from the project list. Anyone who can edit the project can archive or restore it. Archiving hides it from ordinary project lists and pickers and prevents new issues from being created in or moved into it. Existing issues, history, and settings remain; existing issues can still be read and edited. The project's status does not change.
Active autopilots that create issues in the project are paused. To restore the project, switch the project list's title menu to Archived projects and choose Restore, or use Restore project on its page. Restoring does not resume those autopilots; enable them separately when ready.
Create, edit, and delete
Any workspace member can create and edit projects. Members can delete projects they created or that an agent they currently own created; agents can delete only their own projects. Human owner and admin members can delete any project, including older projects with an unknown creator. A private project can only be edited or deleted by people on its member list, so an owner or admin has to be on the list first.
Deleting a project does not delete its issues: they detach and stay in the workspace. The project's description, status, and resources are permanently deleted.
Next steps
- Project resources — link GitHub repositories or local directories.
- Issues — create and organize the concrete work in a project.
- Agents — learn about agent identity, configuration, and Access.