Workspaces

  • Desktop, mobile and web
  • All plans
View as Markdown

What it does

A project in AgentsRoom does not have to be a code repository you already have. A workspace is a project you open from a name, a mission and an agent, with no directory to point at: an incident to handle, a trip to prepare, a product research, a mock-up to build. The app creates the folder itself, outside any repository.

There is no separate kind of project and nothing to switch on. A workspace is a project, with one extra field: its mission, the standing context every agent of that project reads when its session starts, so the brief is never retyped. Memory, skills, backlog, teams, dev commands and the mobile bridge all work on it unchanged. The code-oriented surfaces (Changes tab, branch badge, cloud runs) simply do not show, because there is no git repository, exactly as in any non-git folder.

The mission is not reserved to workspaces: any project can be given one, including a repository.

Where to find it

  • Projects home: the + tile of every zone is split in three. Open project ("Add a folder you already have on this machine"), Create a workspace ("Open a space with no code repository: give it a name and a mission, AgentsRoom creates the folder") and Open the guide.
  • The dialog is New workspace ("No repository: a name, a mission, an agent").
  • Projects home toolbar: New folder creates an empty zone first, so its root folder can be set before the first workspace lands in it.
  • Project settings > General > Mission: read or change the mission of any project.
  • Folder settings > Workspaces: where the workspaces created in this zone are stored, and the zone's memory.
  • Inside a workspace, the mission is shown above the empty state of the room, under the heading Mission.
  • Mobile: the + button in the header of the Projects tab (Add a project) offers the same two doors, Open an existing project and Create a workspace.

How to use it

  1. On the projects home, click Create a workspace on the zone's + tile.
  2. Fill in Name ("e.g. Plan the next trip"). The line Created in {path} shows live where the folder will be made.
  3. Fill in Mission ("What do you want to hand to the agent?"). It rides in the boot prompt of every agent of this workspace.
  4. Pick the Agent. The list starts with Your agents (your saved agent templates, copied whole: persona, provider, model, pinned skills, avatar and name) and then the plain Roles. A saved agent is the point: it arrives with its own notebook and its pinned skills, and a line under the selector says so.
  5. Choose the Folder (the zone it is filed under; No folder for the root), then Create a workspace.

Ask an agent to do it instead: "open a work folder for this incident" makes it call workspace_create, which goes through the very same creation path as the dialog.

To create the zone before its first workspace: click New folder in the projects home toolbar, type the Folder name and press Enter. The zone's settings open straight on the Workspaces tab so you can set its Root folder first. The empty zone stays visible on the home with its own + tile, and the Root folder card of a zone with no project carries a Create the first workspace button that opens the workspace dialog on that zone.

To change where a zone's workspaces land: Folder settings > Workspaces > Root folder (Browse, then Save). Left empty, the app uses the path shown under the field, an AgentsRoom folder in your home directory with one sub-folder per zone.

Settings

  • Mission (per project, Project settings > General): what the project is for, in your own words. Empty by default.
  • Root folder (per folder, Folder settings > Workspaces): where the workspaces of that zone are created. Empty = the default path shown.

Agent tools (MCP)

  • workspace_create: open a new workspace from a name and a mission, optionally a folderName (the zone, by its display name in the sidebar) and a role. Omitting the zone files it next to the project the agent runs in; omitting the role reuses the caller's own role. An unknown or ambiguous zone name is refused rather than silently filed at the root. Nothing is spawned: the workspace is created and selected.
  • Everything else is the ordinary project toolbox: memory_*, skills_*, backlog_*, commands_*.

Providers

All providers, no difference. The mission block is added to the boot prompt whatever CLI the agent runs on, and word for word whether the agent was started from the desktop or from the phone.

Mobile

Since 2026-09-15 a workspace can be created from the phone, on the desktop it is connected to. Tap the + button in the header of the Projects tab, then Create a workspace. The sheet is New workspace with the same four fields as the desktop dialog: Name, Mission ("Every agent of this workspace reads it when a session starts, so you never retype the brief."), Folder (No folder for the root) and Agent (Your agents first, then Roles, with the same "Carries its own memory and N pinned skills" line). The desktop creates the folder through the same path as its own dialog, and the phone opens the new project as soon as it appears in its list.

The same + also offers Open an existing project ("Add a folder you already have on this machine"): the phone has no file picker for a disk that is not its own, so it browses the desktop's directories one level at a time, starting from the home directory, directories only. A folder that already holds a git repository is tagged Git repository, a folder already opened in AgentsRoom is tagged Already a project (choosing it opens that project instead of adding a copy). Use this folder, then Project name (pre-filled with the folder name), Folder and Agent role, then Open the project.

Both entries need a connected desktop: without one they stay visible but disabled, with the note "Connect your desktop to add a project: the folder lives on that computer." The zone list and the saved agents are read from the desktop each time the sheet opens, so a zone created on the desktop a minute earlier is offered. A zone or a saved agent deleted in between is refused with a message rather than replaced silently.

A project's mission also crosses the bridge on its own: the project card shows the mission in place of the last segments of its path, and an agent started from the phone receives the same mission context.

Still desktop only: the New folder button (a zone's root folder is a setting of that machine).

Limits

  • The folder is created under the zone's root folder; two workspaces never share a directory, and a duplicate name gets a numeric suffix.
  • Workspaces count toward the project cap of your plan like any other project. On the desktop, hitting the cap opens the upgrade wall and keeps your text in the dialog; on the phone the sheet shows "Your plan holds all the projects it allows. Delete one to make room, or upgrade to Pro."
  • The mission is written on the project on this machine; it is not synced to the account registry.
  • Cloud agent runs need a git repository, so they are refused in a workspace that is not one. Initialise git in the folder and the git surfaces come back on their own.
  • Nothing distinguishes a workspace from a repository afterwards: there is no filter and no badge, by design. What a project is for is said by its mission.
  • The mobile directory browser lists only the first folders of a very large directory and says so ("Only the first folders are listed.").

Common questions

  • Can I use AgentsRoom for something that is not code? Yes. Create a workspace: a name, a mission, an agent, no repository.
  • Where are my workspace files? In the path shown at creation, under the zone's Root folder (Folder settings > Workspaces).
  • Why is there no Changes tab? There is no git repository in that folder. Run git init there and the git tools appear.
  • My project folder holds several repositories side by side, why does Changes only show one? Because git needs one repository at a time: the tab offers a picker over the repositories found under the folder, and a notice above it names what cannot work at all in that layout (auto-commit when work is done, one worktree per ticket, the diff of a team step), since all three reason about the project root. It is not a supported layout: open each repository as its own project. Said up front since 2026-09-29.
  • Can I change the mission later? Yes, Project settings > General > Mission. It applies to the next session an agent starts.
  • Can I give a mission to a normal repository? Yes, the field is on every project.
  • Can an agent open one for me? Yes, workspace_create. Asked for it, it acts; on its own idea it asks first, because it adds a permanent entry to your sidebar.
  • Can I create a workspace from my phone? Yes, from the + button of the Projects tab, as long as the phone is connected to the desktop that will hold the folder.
  • Can I set the root folder of a zone before creating anything in it? Yes: New folder in the projects home toolbar opens the zone's settings on the Workspaces tab right away.

Related