Project setup

A project holds one engagement: its tasks, the tools and files involved, and the artifacts produced. Everyone with access to the project can use its tools and files. Sessions started inside a project prioritize that context, so the agent does not need to be told which client you mean.

Create a project

There are two ways to create one from Projects:

• New project creates an empty project immediately. Use it when you already have a plan.
• Create project (top right) starts an agent session that plans the engagement with you.

To plan with the agent, describe the engagement: the client, the source and target systems, the scope and the target go-live date. Attach the statement of work and any kickoff notes. The agent drafts tasks with descriptions, dependencies and rough timelines. Review them, adjust, and ask the agent to save the project.

For example:

Plan the migration of Contoso from Dynamics GP to Sage Intacct. Scope: GL, customers,
vendors, open AR and AP, and 24 months of GL history. Go-live is 1 December.
Use the kickoff notes from last Tuesday's Circleback meeting.

i

A planning request does not start execution. The agent creates the project and tasks, and nothing is written to a client system until you ask for it and approve it.

Work with tasks

A project opens as its folder under Brain, with a Files tab and a Tasks tab with Board and Table views.

Each task has a status (Not started, In progress, Waiting or Done), an optional due date and assignee, labels, and a description. Use Waiting for tasks blocked on the client, such as missing credentials or an unanswered mapping question. Drag a task to reorder it in its column, for example to put the most important task at the top, or drop it at a position in another column to change its status. New tasks go to the end of their column. Keep mapping decisions, validation rules and cutover details in the task descriptions, so the trace of why a decision was made stays with the work.

Labels group tasks across columns, for example by workstream or by blocker type. Each project has its own labels. Open a task and select Labels to add a label, or type a new name to create one with a color from the palette or any hex color. Manage all labels of a project through Labels in the project menu. The label filter on the Tasks tab shows the tasks that have any of the selected labels, and it combines with the assignee filter.

The agent updates tasks as it completes work in a project session. You can also ask it to reprioritize, add tasks after a scope change, or summarize progress for a status call.

Add files

A project’s files live in its folder in Brain. Drop the exports the client sent onto the folder, or open the folder and upload them, so every session starts with them in reach. A file can be in several projects. Tasks have no attachments; name the file a task needs in its description.

Linking a resource does not grant access to it. Team members still need their own connection to each client system and the usual access rules apply. See Handover for sharing.

Share, archive and close

Projects can be shared with team members, archived when the engagement ends, and deleted. Archiving hides the project and its sessions from the sidebar and blocks further task changes, while the run history and artifacts remain available. Deleting a project permanently removes it and its tasks; its sessions stay available without a project.