Projects group a team’s bots, threads, and shared objective. Al is the project coordinator: it plans and routes work, reports completion or blockers, and collects results. Assigned bots execute the work.

​
Start a project

  1. Choose New project in the rail to create a project and open its home. Name it there.
  2. Add the bots that will work on the project, or start from a team template.
  3. Give Al a concrete brief: the desired result, inputs, constraints, and what needs your review.
  4. Open the resulting thread cards to inspect work, steer a bot, or stop an active turn.
  5. Review the results and resolve completed task threads.
For example: “Research these three competitors, draft a comparison brief, then prepare launch copy from the reviewed brief.” The research can run independently; the dependent drafting work follows its prerequisites.

​
Planning and execution

The coordinator validates a proposed plan against the available team, rejects dependency cycles, and limits model-generated plans to six steps. Independent threads start in parallel. Dependent threads remain queued until their prerequisites reach review or done. A completed kickoff turn moves to review and posts a short report to project chat. Review is a work status. If your process requires explicit approval before the next task starts, include an approval gate in the template or task instructions; dependency readiness alone does not prove human approval. If planning is unavailable or returns an invalid plan, the coordinator falls back to one thread for the best-matching bot. A project with no available team can return a no-team response. Follow-up routing is restricted to open threads in that project.

​
Steer and inspect

Project messages carry receipts for fan-out, routing, completion, blockers, and synthesis. Follow-up messages can go to an existing thread rather than starting a fresh plan. The thread list shows server status and checklist progress, so reopening Project home exposes work that started elsewhere. For Code and Cowork project workspaces, the registered project settings include context and directory. The project folder is supplied as the session work directory; choosing a project should give the agent the project context it will actually use.

​
Runtime API

These are authenticated private data-plane routes, not a promise of public Cloud API availability. The start request takes threads, each with threadId and text. It returns accepted and skipped thread ids after accepting background execution; an accepted request is not a finished deliverable. See threads, templates, and the Allternit Factory.

​
One bot project list

The Bot filter in Projects and the project list in Bot Mode read the same server team projects. Cards show the project’s description, team, and thread counts. Choose New with the Bot filter selected to create a project and open its page in place. Pin a project from its page or card; use the project options menu to archive it. Show archived projects to return to them.

​
Project context and settings

Context files are stored with the server project and sync across devices. Add or remove them from the project’s details card. The Folder is a per-device working directory: a path chosen on one device is not a shared folder on another. Folder picking is offered only where that device supports it. Project settings include icon, colour, and coordinator instructions. Coordinator instructions save to the server project; default icon, colour, and folder are per-device workspace settings. Custom project and folder appearances are personal preferences saved on the connected runtime and loaded by devices using that runtime and account. A bot project does not have project model or permission selectors. Each thread gets its model and permissions from its bot. Change the bot configuration for that worker rather than expecting a project setting to override it. Other project modes can expose their own coordinator and thread model settings.

​
Inspect project work

The bot project page has one docked pane with Threads · Library · Routines · Browser in its view menu. Opening the pane collapses the details card to leave room for the work. Threads are grouped by work status. Open the graph to inspect dependencies, or open a thread card to see its conversation. Library collects project outputs; Routines exposes project schedules; Browser opens the project browser. Projects-tab workspaces also show grouped threads, a dependency graph, coordinator receipts, thread chips and pills, wrap-up reports, decision cards for work that needs you, and a Library of outputs. Receipts report routing and execution state; review the underlying thread and deliverable before accepting the result. On the phone, a thread tap opens the pane full screen. Its slim bar keeps the view menu and available actions reachable, and Back returns to the project conversation. On a bot project, use the details toggle to reach Context, Folder, team, Library, and Routines; Browser is also available from the pane menu. Pin, archive, and project settings remain available. These paths are shared by the web phone layout and PWA.