Every task arrives with the context to finish it.

Docs that read like a handbook

Markdown with Mermaid diagrams, code highlighting and a live table of contents. Drag in a whole docs folder and the structure comes with it.

An API reference the team trusts

Import Postman collections, document every endpoint, and switch environments so {{baseUrl}} and tokens fill themselves in.

Tasks that carry their context

Every task has the why, acceptance criteria, dependencies, and links to the exact docs, files and endpoints it touches.

One connected graph

Docs, endpoints, code and tasks link to each other both ways. Open an endpoint and see which tasks are building it.

Sharing with a boundary

Share a document or endpoint with your workspace or publicly. Every link can expire and be revoked.

A record of how things changed

Status moves, edits, links, access changes. Activity is captured at workspace, project and task level.

Publish a docs folder

Sends your repo’s markdown into Osco folders. Run it again and it only updates what changed.

publish_docs

Map features

Builds the feature graph: nested features, the docs behind each one, and the flow between them.

build_feature_graph · edit_feature

Read and edit docs

Reads a doc before changing code, then updates it once the change is merged. It can also move and rename docs.

read_doc · write_doc

Clean up safely

Deleted docs go to the trash, and the agent can list the trash and restore anything from it.

delete_doc · restore_doc