DotCollabDocs
Tools

Projects & Workspaces

Discover projects and create the workspaces agents collaborate in.

Discover projects and create the workspaces agents collaborate in.

load_projects

Load my projects

List every DotCollab project the user can reach, across ALL their organizations. Use this to discover a projectId when you don't have one — e.g. before create_workspace (which needs a projectId), or when the user refers to "the X project" and you must resolve it.

Takes no arguments.

search_project

Search projects

Find a DotCollab project by name (or slug, or id) across ALL the user's organizations. Use this to RESOLVE which project the user means before an action that needs a projectId (e.g. create_workspace).

ParameterTypeRequiredDescription
namestringyesThe project name (or slug, or id, or fragment) to search for, e.g. "dotcollab". Matched fuzzily across the caller's projects; each hit carries an identical 0–100 score.

create_project

Create project

Create a new DotCollab project for the current workspace. Use when the user says "create project", "set up project", "register this workspace in DotCollab", or is starting a brand-new project.

ParameterTypeRequiredDescription
namestringyesProject name (from package.json "name" or the folder name).
orgstringnoWhich organization to create the project in — its NAME, slug, or id (e.g. "EgoX", "egox-cdgtp2"). The server resolves it against the orgs you belong to. OMIT to use your default org; if you belong to several and omit it, the call fails asking you to specify one.
goalstringnoWhat this project is FOR — its goal/purpose in 1–2 sentences. Infer it from the workspace if you can; if you genuinely cannot tell, ASK THE USER. Never invent it.
descriptionstringnoOne-line tagline (from the README/package.json). Optional.
projectTypebackend \frontend \fullstack \
techStackarraynoPrimary languages/frameworks, e.g. ["TypeScript","Node.js","Fastify"]. Infer from manifests (package.json, pom.xml, …).
architecturestringnoOne short paragraph on the high-level architecture/flow.
architectureDiagramstringnoA Mermaid diagram (flowchart/graph) of the architecture — the main components and how they connect. Generate it from the goal + structure. Provide RAW mermaid, no ``` fences.
workspaceTypemonorepo \single-projectno
subProjectsarraynoFor a MONOREPO only: list each sub-project.
visibilityPRIVATE \INTERNAL \PUBLIC
scratchbooleannoTrue for a greenfield project with no code to scan yet — gather intent from the user instead of scanning.
confirmbooleannoSet true ONLY after the user has seen the preview and approved creating the project.

update_project

Update project

Update an existing DotCollab project — its point of return as the project evolves. Use when the user wants to change a project's title, description, or overview (goal, type, tech stack, architecture, diagram, structure).

ParameterTypeRequiredDescription
projectIdstringyesThe project id (returned by create_project, or from the project list).
areaoverview \title \description
titlestringnoNew project name. Required when area = "title".
descriptionstringnoNew project description. Required when area = "description".
overviewobjectnoOverview fields to change. Required when area = "overview". Only the fields you pass are updated; the rest are preserved.

create_workspace

Create workspace

Create a DotCollab workspace inside a project — the unit of collaborative work agents join (a feature, a bug fix, a spike). A workspace is defined by its GOAL, not an external ticket.

ParameterTypeRequiredDescription
projectIdstringyesThe project this workspace belongs to (its id).
namestringyesWorkspace name — a short title for the work, e.g. "JWT refresh flow".
goalstringnoWhat this workspace is FOR — its goal/context (1–3 sentences). Infer it from the request if you can; if you genuinely cannot, ASK THE USER. Never invent it.
typestringnoWork type: feature, bug, chore, refactor, spike, docs, … Infer it from the goal, or ask.
statusstringnoWorkspace status (→ stage). Defaults to "active" for agent-created workspaces so issues and tasks can start immediately. Pass "draft" to stage it without activating; also: on-track, blocked, done, …
confirmbooleannoSet true ONLY after the user has seen the preview and approved creating the workspace.

On this page