The Project Manager

Every project on your account and the agents allowed to work in each — where memory is switched on per project, where conversations are brought in, and where an agent's memory is cleared.

The Project Manager button in the menu bar — the first of the three workspace icons, before Task Manager and Agent Composer — opens a tab with two tabs of its own across the top: Projects and Your Agents. They're the same information read along two axes: a project and the agents allowed in it, or an agent and the projects it's allowed in.

These are the projects on your account, so the list can include ones registered from another machine. The project you have open is marked, and is what the tab opens on.

Projects#

A rail down the left lists your projects newest-work-first, grouped by when you last worked in them, with a conversation count on each row. New project sits at the head of the list — the same form the project chip's menu opens. Search filters by name or path.

Pick one and its page opens, titled with its name and how many sessions it has had — (132 sessions). A Load button on the title line opens it in the IDE; the project you already have open has none. Down the page:

Name. What the project is called. Renaming changes it everywhere — here and in the Open Project list — and is a label only: the folder on disk keeps its own name.

Memory. The per-project switch. Conversations here recall past work and the memory walker writes to the project's agent. Off: Nothing is recalled and the memory walker has nowhere to write. Turning this back on keeps the agents and memories below — they are not deleted by the switch. A project set up without memory has this off and no agents; nothing will be made until you turn it on.

Conversations. Two things live here. Import from Claude Code… brings the chats you had with Claude Code in this project into the history, where they show up like any other conversation. Nothing is imported twice, and a Delete N imported button appears afterwards for the ones that came in that way — Studio's own chats are never touched by it. Below that, the ingest panel counts the conversations not yet in memory and runs the walker over them in bulk.

→ Bringing many conversations in at once

Agents. The roster allowed to work in this project. ★ marks the default — what new conversations use; home marks the one project an agent belongs to. Each row shows the agent's memory count and size, and a Clear memory button.

Important

Clear memory deletes everything that agent remembers — all 132 memories of Studio. It cannot be undone — after a confirmation that quotes the real count. The agent itself stays, with its name and its projects. For the project's default agent the ingest ledger is reset too, so the next ingest reads the whole history from the start. It waits while an ingest is running for this project.

Workspace. Where the project lives on disk, and when you last worked in it.

Forget this project. Removes the project from Semantix — the project, its conversations, and the agents that work nowhere else, with their memory. An agent that also works in other projects is kept; only what it remembers about this one is deleted. You're shown the exact counts first, in a dialog titled Forget ?, and your files on disk are never touched. Forgetting the project you're standing in lands you on the welcome screen.

Your Agents#

Your agents, each with its own memory, owned by you rather than by any project. The rail lists them; New agent makes one from a name and a description.

Pick an agent and its page shows its memory count and size, a Rename button (The name is a handle. This agent's memories and projects follow it, not the word.), and a section for this project — the one you have open:

  • Allow here — lets the agent work in the open project. Nothing is copied; the agent brings its memory with it.
  • Make default — new conversations in this project will talk to it. The starred one.
  • Make home — makes this the one project the agent belongs to. Home starts where an agent was first posted and moves when you say so.
  • Remove — takes it off this project's roster. Its memory is untouched.

On the roster page each agent's row reads its marks against the open project: default here, allowed here, home.

Note

An agent's name is how the Set up this project dialog reuses one: name the default agent after an agent you already have and that agent is allowed into the new project, memories and all, rather than a fresh one being made. The dialog says so before you commit.

When the server is away#

Both tabs read from the Semantix server. Offline, the page says Not answering with a Retry button, and the rail's footer reads server offline. Your files and your conversations on disk are unaffected; only this view is.

→ Memory · What's stored, and where