nyxdoc
ENKOJA
GitHub

MIT open source · Self-hosted · MCP/API

Bring the agents you already use into a shared document workspace.

Nyxdoc is not a chatbot inside your docs. Connect Codex, Claude Code, OpenClaw, or any MCP client. Agents create and update a shared draft; people review, edit in the browser, and decide when to save the next version.

View on GitHubInstall with Docker
  • External agents, not an embedded chatbot
  • Shared drafts with explicit saves
  • Rich documents with attributable revisions
Nyxdoc workspace showing a document tree, an open document, and explicit save controls
FIG 01One document tree for people in the browser and external agents over MCP.

Documents are the common surface

Agent work should end in a document people can keep using.

Code repositories are useful for files, and chat is useful for requests. Neither is a comfortable place for a team to read, revise, and preserve everyday knowledge with an agent.

01

Git and Markdown

Good history, but images, rich tables, navigation, and small human corrections still create friction for many teams.

02

Notion or Confluence with MCP

Best when external agents should work inside an existing SaaS knowledge base.

03

Nyxdoc

For people and external agents working on the same rich draft, with direct editing, explicit saved versions, and self-hosted deployment.

Shared draft → Human review → Saved revision

Read the product vision

A visible working loop

From request to saved revision in four steps.

The agent stays in its usual client. Nyxdoc provides the document context, permissions, draft, and revision record.

  1. 01

    Connect your agent

    Register an external agent with OAuth or a scoped connection key, then choose its workspace and document permissions.

    Codex · Editor · Product subtree
  2. 02

    Describe the document work

    Ask in your usual agent client, or leave an Agent To-do and explicitly tell the agent when to begin.

    Update the launch FAQ with the confirmed date
  3. 03

    Work in a shared draft

    The agent reads the document tree, edits structured content, uploads media, and returns its work to the document.

  4. 04

    Review and save

    A person checks the result, makes final edits, and explicitly saves a revision with its author and change summary.

Nyxdoc rich document editor with structured content, images, and a document tree
FIG 02A rich document stays readable and editable in the browser.

One document, two working surfaces

People and agents use the interface that fits their work.

Nyxdoc does not ask people to edit JSON or ask agents to operate a visual editor. Both sides meet in the same structured document and revision model.

  • For peopleRead a document tree, paste images, edit rich content, assign work, inspect changes, and save when ready.
  • For external agentsDiscover capabilities, search by structure, batch-read context, patch blocks, upload media, and commit with version checks.
  • One shared draftReading and cursor movement do not create a revision. The canonical history changes only after an explicit save.
Read the document model

If error rate exceeds 2%, stop the rollout and restore version 17.

FIG 03 — People can make precise final edits without leaving the document.

Review what changed

A saved version should explain itself.

See who changed a document, what they changed, and why. Open earlier revisions without creating new ones, compare content, and restore deliberately when needed.

Shared draft versus saved version
Compare current work with the latest canonical revision before deciding to save.
Attributable history
Human and agent authors, summaries, and revision numbers remain attached to each saved version.
Deliberate restore
Viewing an old revision does not change history. Restoring it creates a new, explicit revision.
Read about drafts and revisions
FIG 04Review the agent's changes before they become the next saved version.
FIG 05Every saved revision keeps its author and change summary.
FIG 06Your agent remains external. Nyxdoc is the shared document system it can safely use.

Bring your own agent

Use the agent client that already fits your work.

Nyxdoc is vendor-neutral. Connect through Streamable HTTP MCP or the API instead of moving your workflow into another embedded assistant.

  • CodexConnect over MCP and work from an existing Codex task.
  • Claude CodeUse the same capability and document contracts from Claude Code.
  • OpenClawGive a long-running agent scoped access to the documents it maintains.
  • Any MCP clientUse published schemas and capability discovery instead of client-specific behavior.

Agent identity, credentials, workspace assignments, document range, and permitted actions are managed separately.

Read the agent protocol

Start alone, add a team when needed

The same document model works for one person and a small organization.

A personal workspace stays simple. Organizations and teams add clear ownership and access boundaries without changing how documents work.

  1. 01

    Personal workspaces

    Keep projects separate and decide what each of your agents can read or change.

  2. 02

    People and teams

    Invite members and group access by team while preserving individual attribution.

  3. 03

    Shared agent identities

    Register an agent once, then assign different roles and document scopes per workspace.

  4. 04

    Assignments and recovery

    Coordinate Agent To-do work and retain trash, restore, and audit records across contributors.

Agent To-do in Nyxdoc showing a document request, target document, assigned agent, and human review requirement
FIG 07An explicit Agent To-do keeps the document request, target, assignee, and human review handoff visible.

Open source and self-hosted

Keep the document system under your control.

Nyxdoc is released under the MIT License. Run it on your own Linux host with Docker Compose, inspect the source, and adapt it to your environment.

  • MIT licensedUse, study, modify, redistribute, or build a service with Nyxdoc.
  • Your instanceDocuments, media, identities, and revision history remain in the environment you operate.
  • Docker ComposeInstall on a Linux host with a documented, reproducible setup.
  • Manual updatesA single update script runs the required application and database migrations.
  • Clean removalUninstall with one script, with an explicit option when you also intend to remove data.
  • No external telemetry requiredRun the public release without sending product analytics to a third-party service.
QUICKSTART
git clone https://github.com/getnyxdoc/nyxdoc.git && cd nyxdoc && ./scripts/install.sh

Linux host · Docker Engine · Docker Compose v2

Install NyxdocOpen the repository

Give agent work a place people can review, revise, and keep.

Install Nyxdoc on your own host, connect the agent you already use, and begin with one real document workflow.

View Nyxdoc on GitHubInstall with Docker