Skip to content

Project setup

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

Everyone with access to the project can use its tools and files.

Start a project from Start a project on the home screen, or from New project in the project switcher. Both start an agent session that plans the engagement with you.

  1. Select Start a project or New project.

  2. Describe the engagement: the client, the source and target systems, the scope and the target go-live date. 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.
  3. Attach the statement of work and any kickoff notes.

  4. Review the tasks that the agent drafts, with descriptions, dependencies and rough timelines.

  5. Adjust the tasks.

  6. Ask the agent to save the project.

A project opens as its folder under Brain, with the brief, the progress of the plan, the task Up next and the files. View plan opens the tasks in Board and Table views.

Project plan of a migration project in Board view, with columns for Not started, In progress, Waiting and DoneProject plan of a migration project in Board view, with columns for Not started, In progress, Waiting and Done
The project plan in Board view. Start opens a session for the task.

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.

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.

Drag a task to reorder it in its column, for example to put the most important task at the top. Drop it at a position in another column to change its status. New tasks go to the end of their column.

Labels group tasks across columns, for example by workstream or by blocker type. Each project has its own labels.

  1. Open a task and select Labels.
  2. 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 in the plan shows the tasks that have any of the selected labels. 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.

superglue prepares open tasks in the background. Each weekday, the briefing turns open tasks into next steps and starts superglue’s work on the steps it can do itself. A run that needs your decision or a write waits until you answer.

Up next on the project folder and Next steps on the home screen show the prepared work. Your briefing sends the same next steps to Microsoft Teams or by email.

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.

Access to a project gives the same access to its linked files and tools. Connections and playbooks are not shared this way: team members still need their own connection to each client system. See Handover for sharing.

Project folder in Brain with plan progress, the next task and a saved audit fileProject folder in Brain with plan progress, the next task and a saved audit file
The project folder in Brain shows the progress of the plan and the files the agent saved.

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. Access that people had only through the project ends.

Deleting a project permanently removes it and its tasks. Its sessions stay available without a project.