Publish with your agents

Docs, help articles, blog posts and wikis, drafted and kept current by Workover AI and the coding agent you already use. Your team approves what ships.

Works with Claude Code · Cursor · Codex

Set up Workover for me, follow the instructions on workover.io/setup.md

Paste it into your agent, or set it up by hand.

Or start a 14-day trial
Pull request 482 merges into main. Workover AI finds one article it affects and drafts a suggested update: in step 1 of Connecting your WordPress site, Integrations becomes Settings, then Connections, with Edit and Accept. Demo workspace.

Docs that change when your code does.

Connect the Workover GitHub App and pick the branch to watch. On each merge, Workover reads the change and drafts the doc edits it calls for, so the docs move when the product does.

  • Finds what it touches

    It shortlists the articles a merge affects and checks each one against your repository before it drafts.

  • Drafts the edit

    Edits arrive together as one change request, labeled Workover AI. When a change needs a new article, it drafts that too.

  • Before the merge, if you like

    Turn on pull request review for a project, and Workover drafts the docs while the pull request is still open.

Nothing ships until a person says yes.

Agents draft. People decide. Every change arrives in the editor as a tracked suggestion, for someone who knows the product to accept, edit or dismiss.

  • Suggestions, never edits

    Workover AI drafts. A person accepts, and publishing is a separate step.

  • Credited to its source

    Each change says where it came from: Workover AI, or a person and their tool, as in Dan Ortiz via Workover CLI.

  • An approval gate when you want one

    Ask people by name to approve a page, and it cannot publish until they do.

The Workover editor reviewing the article Single sign-on: Dan Ortiz, through the Workover CLI, suggests 4 changes, shown as tracked changes with Accept all and Dismiss, and Maya Kim has commented on the words within five minutes.

Updates start wherever the change does.

A merge is one signal. Workover also listens where your team hears about change first, and drafts from there.

  • Your support inbox

    Workover reads your Zendesk, Intercom, Help Scout, Freshdesk or Plain conversations, finds the questions your team keeps answering by hand, and drafts the article. At most three a week per project, each citing the answers it came from, redacted.

  • A change you describe

    Tell the agent what changed, with screenshots if you like, in Workover or by mentioning @Workover in Slack. It replies in the thread when its suggestions are ready.

  • Your coding agent

    Claude Code, Cursor or Codex reads your docs and proposes changes through the Workover CLI and MCP server, checked against your style guide. Set it up below.

Set up Workover in your agent.

Sign in once with the Workover CLI, then add the MCP server. Whatever your agent proposes arrives as suggestions, like everything else.

npm i -g @workover/cliworkover login --client "Claude Code"claude mcp add --scope user workover -- npx -y @workover/mcp@latestworkover install-claude

The last line is optional: a skill that opens a pasted Workover link with the CLI.

Another MCP client? Add a local stdio server that runs npx -y @workover/mcp@latest.

Full setup guide →

Know which pages have drifted.

Not every change comes with a pull request. Health checks your published articles against your product weekly and flags what no longer matches, so you fix the page before a customer finds it.

  • Health

    Weekly, or whenever you click Run check. Each finding says what is wrong, and Workover AI can draft the fix as a suggestion.

  • Verified by a person

    Mark a page verified for as long as it should hold, and keep the record of who drafted, accepted and approved each change.

    Verification →

Questions

No. Workover AI drafts suggestions. A person accepts them, and publishing is a separate step. Add an approval gate, and only approved pages go live. Workflows and approvals

See your first suggested updates this week.

Import them from their address, connect GitHub, and review the first suggested updates in your own workspace.