Docs

Setup guide

Install the app, connect Jira and Bitbucket, anchor your first pages, and let your agents check pages before they cite them. You can see the whole flow without Bitbucket by replaying the demo pull request.

Before you start

  • Confluence Cloud, and a site admin to install the app. Confluence administrators change its settings.
  • Jira Cloud on the same site, if you want Jira issues as anchors or want to create Jira tasks. Optional.
  • A Bitbucket Cloud team workspace, if you want merged pull requests to flag pages. Forge apps can't be installed in personal workspaces. Optional: the demo replay works without it.
  • Rovo on the site, for the Drift Reviewer agent and Propose fix. Everything else works without it.

Doc Drift is two Forge apps: the main app in Confluence, and a small relay in Bitbucket that sends merged pull requests to it. Forge doesn't let one app span Bitbucket and Confluence, so the relay is separate.

Install the app

The install link is shared with Codegeist 2026 judges first and will be posted here. If you're a judge, use the link on the Devpost entry.

  1. Open the install link and pick your site. Only a site admin can install.
  2. Review the permissions and select Install. Confluence is required; you can also connect Jira here.
  3. Open any published page. A Doc Drift item appears in the byline, under the title.
  4. Click it once and allow access when asked. The app and your agents act as you, so each person grants this once.

Connect Jira

Jira is optional. With it, a page can be anchored to an issue or epic, and changes to its status, resolution, fix versions, components, summary, description or parent flag the page. You can also create a Jira task from a flagged page.

If you skipped Jira at install, connect it later in Atlassian Administration:

Apps › Sites › your site › Connected apps › Doc Drift › View app details › Connections › Jira › Connect

To turn Jira changes off without disconnecting, use Jira in the app settings.

Connect Bitbucket

The relay reads each pull request merged into a repository's main branch, and sends Doc Drift the list of changed files and a short diff. It signs every request with a secret that only your site and the relay know.

  1. In Confluence, open Settings (the gear), then Doc Drift in the sidebar. Under Bitbucket relay, copy the ingest URL and select Generate secret. Copy the secret now: it's shown only once.
  2. Install the Doc Drift Relay in your Bitbucket team workspace with its install link.
  3. In Bitbucket, open Workspace settings, then Doc Drift Relay under Forge apps. Paste the URL and the secret and select Save.
  4. Select Send test ping. It should say Connected, and the Confluence settings page shows the time of the last ping.

Merge a pull request and the settings page lists the repository under Repositories seen. Rotating the secret stops the old one at once, so update the relay right after.

Try the demo replay

The demo replays a seeded pull request through the same path the relay uses, with no Bitbucket needed. PR #482 in payments-api renames scripts/rollback.sh to scripts/rollback-v2.sh, and ROLLBACK_TIMEOUT to ROLLBACK_TIMEOUT_SECS.

  1. Make a page that mentions scripts/rollback.sh, publish it, and anchor it to repository payments-api, path scripts/rollback.sh.
  2. In the app settings, under Get started, select Replay seeded PR #482.
  3. After a few seconds, reload the page. The badge reads Possibly stale. Open it to see the change, the affected step and the rename quick fix.

Set the comment delay to 0 minutes in settings if you want the owner comment to appear straight away.

Anchor pages

An anchor links a page to something it describes. When that thing changes, the page is flagged. Click the Doc Drift badge on a page and open Anchors.

AnchorExampleFlags the page when
Filepayments-api: scripts/rollback.shThe file is changed, renamed or removed
Folder or globpayments-api: deploy/helm/**Any matching file changes
Jira issue or epicPAY-142Its status, scope, fix versions or parent change
Whole repositorypayments-apiLarge changes only. A weak anchor: prefer paths
  • Suggestions. Doc Drift reads the paths in code blocks, Bitbucket links and Jira keys on the page and suggests them. Tick the ones that fit and save.
  • Critical anchors. Mark an anchor Critical when a change to it should always get attention, such as the script a runbook runs.
  • A whole space. On a space's Drift dashboard, select Anchor this space to review suggestions for every unanchored page in one table.
  • Save anchors and mark verified saves them and marks the page Verified. Changing anchors needs edit rights on the page.

Review a flagged page

Click the badge on a Possibly stale or Stale page. The Review tab lists each change: the pull request or Jira change, who made it, when, the files, and a sentence on why it flagged this page. Below that are the page sections that mention what changed.

ActionWhat it does
Mark verifiedYou checked the page against the change. Closes the open changes and records who verified.
Propose fixOpens Drift Reviewer in Rovo, which drafts new text per affected block. Drafts appear in the panel; nothing changes until you accept.
Accept fixSaves the draft as a new page version, as you, with a message naming the pull request. Needs edit rights.
Rename quick fixFor a renamed file, replaces the old path with the new one in the affected blocks. No AI.
Snooze 7 daysHides the change for a week. The page stays flagged for agents.
DismissCloses the change with a reason: not relevant, already updated, or false positive. Not relevant can also stop watching that path for this page.
Create Jira taskCreates a task as you, listing the changes and sections to re-read. Closing the task doesn't verify the page.

Space dashboard

Each space has a Drift dashboard in its sidebar: how many pages are anchored, how many are Possibly stale or Stale, the median time to verify, the pages that need a review most, and a backlog by owner. Select a row to open the page.

Settings

Confluence administrators find the settings under Settings, then Doc Drift. Changes apply to the next change the app receives.

SettingDefaultWhat it changes
SensitivityBalancedHow strong a match must be to flag a page: Strict, Balanced or Quiet
Ignored pathsTests, lock files, snapshots, build output, MarkdownFiles that never flag a page, as globs
Only count merges into the main branchOnMerges into release or feature branches never flag a page
Watched spacesAll spacesPages outside the chosen spaces keep their anchors but aren't flagged
Escalation7 daysHow long a page stays Possibly stale before it turns Stale
CommentsOn, 10 minute delayThe owner comment, and how long to wait so changes that land together become one comment
JiraOnWhether Jira issue changes flag pages

Connect coding agents

Doc Drift has an MCP server with three read-only tools: check-page-freshness, find-docs-for-path and list-stale-pages. Agents sign in as a person and only see pages that person can view.

  1. An admin turns on the tools. In Atlassian Administration: Apps, Sites, your site, Connected apps, Doc Drift, View app details. Under Tools, turn on the tools to share with MCP clients.
  2. Open the app once in Confluence and allow access, if you haven't yet. Signing in to the MCP server doesn't grant this.
  3. Add the server. In Claude Code, run the command below, then /mcp in a session to sign in and pick your site.
claude mcp add --transport http doc-drift https://mcp.atlassian.com/forge/12e968a1-a45d-4524-ba28-d47e2315db1a

Cursor and other clients

Add a remote server with this URL. In Cursor, put it in .cursor/mcp.json or ~/.cursor/mcp.json:

{ "mcpServers": { "doc-drift": { "url": "https://mcp.atlassian.com/forge/12e968a1-a45d-4524-ba28-d47e2315db1a" } } }

Tell the agent when to use it

Paste this into CLAUDE.md or AGENTS.md. The same text is in the app settings under For coding agents.

Before you rely on a Confluence page, call the `check-page-freshness` tool from the doc-drift MCP server with its page ID or URL. If the state is not `verified`, do not present its steps as current, and tell the user which page needs a review. When a page and the code disagree, trust the code.

The tools

ToolInputReturns
check-page-freshnessPage ID, URL or exact titleThe state, open changes, affected sections, a cite policy and guidance on how to cite the page
find-docs-for-pathRepository and a file, folder or globUp to 25 pages anchored to that path, each with its state
list-stale-pagesOptional space key and limitPossibly stale and Stale pages, most urgent first

Drift Reviewer in Rovo

Drift Reviewer is a Rovo agent that answers freshness questions and drafts fixes. Find it in Rovo Chat, or select Propose fix in the review panel to open it with the page.

  • Ask “Is this page still current?” or “What changed since this page was verified?”
  • Ask it to draft a fix. Each draft replaces one block, Rovo asks you to confirm before it's saved, and you accept it in the review panel.
  • Tell it you checked the page, and it can record a verification for you after you confirm.

Drift Reviewer never edits a page, and treats page and diff text as evidence, not instructions. Drafting uses Rovo credits on your site.

Page states

StateMeansAgents are told
VerifiedChecked since its anchors last changedSafe to cite
Possibly staleAn anchor changed after the last verificationCite with a caveat that names the change
StaleUnreviewed for 7 days, 3 or more open changes, or a further high change to a critical anchorDon't present its steps as current
UnanchoredNot linked to code or Jira yetCan't tell if it's current: cite with care

Troubleshooting

An agent tool says to grant access in Connected apps

The person signed in to the MCP server hasn't opened the app in Confluence yet. Open any page, click the Doc Drift badge and allow access, then retry. After an app upgrade that adds permissions, do this once more.

There's no badge on a page

Confluence shows app byline items only on published pages. Publish the page and reload it.

A page with view restrictions can't be anchored

Restricted pages can't be watched yet: the app can't read them, and their changes don't reach it. Agents are told to check those pages against the code before citing them.

A merge didn't flag the page

  • The merge went into a branch other than main. Only main-branch merges count.
  • The changed file matches an ignored path, such as a test or a Markdown file.
  • The page is in a space that isn't watched.
  • The match was weak, for example a whole-repo anchor on a small change. Anchor the exact path, or try the Strict preset.

The relay test ping fails

Check that the URL and secret match the ones in Confluence settings. If you rotated the secret, paste the new one. In a personal Bitbucket workspace the relay can't be installed: use a team workspace.

The badge didn't update after an action

Reload the page. The badge state is stored with the page and refreshes on the next load.

Support

Email hello@nano-soft.tech, or open an issue on GitHub. Say what you did, what you expected, and what happened. Leave out page content and secrets.

Doc Drift is made by Nano-Soft Technology SRL (Nano Soft), Bucharest, Romania.

For how the apps handle data, see Privacy and data handling.