Projects

Projects organize documents inside a workspace. They are useful when an agent publishes a batch of related docs and you want that work to stay separate from the workspace's main document list.

Every workspace has a non-deletable Default project. If you never create another project, OpenDocs behaves like a simple workspace-level document library.

When to use a project

Use a project when a set of documents belongs together:

• launch plans and campaign docs
• agent-generated implementation notes for one feature
• client deliverables
• research batches
• test runs you do not want mixed into the main workspace

Use tags for smaller labels inside a project. A good mental model is:

workspace -> project -> docs + tags

For example, a Launch Strategy project might contain docs tagged x, reddit, copywriting, and budget.

URLs

Default project docs keep the short workspace URL:

https://opendocs.cc/<workspace>/<doc-slug>

Non-default project docs include the project slug:

https://opendocs.cc/<workspace>/projects/<project-slug>/<doc-slug>

Tags are scoped the same way:

https://opendocs.cc/<workspace>/tag/<tag>
https://opendocs.cc/<workspace>/projects/<project-slug>/tag/<tag>

CLI workflow

List projects in the active workspace:

opendocs project list

Create a project and immediately switch to it:

opendocs project create "Launch docs" --slug launch-docs --use

Publish into the active project:

opendocs publish launch-plan.md --tags strategy

Or publish into a specific project without switching:

opendocs publish launch-plan.md --project launch-docs --tags strategy

Check the current workspace and project:

opendocs whoami

Switch back to Default:

opendocs project use default

Switching workspaces with opendocs workspace use <workspace-slug> resets the active project to that workspace's Default project.

Listing and pulling

opendocs list shows the active project by default:

opendocs list

List across every project in the active workspace:

opendocs list --all-projects

Pull one project:

opendocs pull --project launch-docs --output ./launch-docs

Pull the whole workspace:

opendocs pull --workspace --output ./opendocs-export

Workspace pulls write Default project docs at the output root and non-default project docs under projects/<project-slug>/.

Agent guidance

When an agent is publishing one-off docs, the Default project is fine. When it is publishing a batch for a named task, ask it to create or switch to a project first:

opendocs project create "API migration" --slug api-migration --use --json
opendocs publish ./migration-docs --tags migration --json

This keeps the workspace profile easy to browse and gives humans a clean project URL to review.