Coding-agent sync · Beta · Pro and Business
Articles that update when you ship.
The coding agent that wrote the change runs the helprism-sync skill at PR time. It writes a one-line impact note, drafts the full rewrite where a sentence a customer reads became wrong, and sends it to the Changes inbox. A person accepts. Readers see the date.
Set up sync · Read the skill · Start free trial
Claude Code, Codex, Cursor · The diff stays on your machine · Nothing auto-publishes
Three doors, one place to review
The agent door is the primary one and does the judging on your machine. The two server doors are optional, for teams that want it out of the coding session. Every door lands in the same workspace, and nothing publishes without a person.
Agent skill (primary, beta; Pro and Business)
The helprism-sync skill runs in Claude Code, Codex or Cursor at PR time, in the session that wrote the change. Your model judges and drafts with the diff in front of it. Helprism receives the finished drafts, never the code. Ask your agent: "Run helprism-sync on this change."
GitHub App (optional, beta; Business)
A merged pull request or a push to your default branch sends the changed file paths and the commit messages. Helprism's server checks which articles the change touches and puts them on the freshness list to verify. The workspace owner connects it from the Sync page. Permissions: pull_requests:read, contents:read, issues:write, metadata:read.
CLI (optional, beta; Business)
From GitHub Actions or any CI on push to main. It reads the git log for the range, sends file paths and commit messages, and never runs git diff. A dry run prints exactly what would leave: npx -y @helprism/cli@latest sync --since <ref>
The agent door is never capped. The GitHub App and the CLI share 500 events a month per workspace, and a change with nothing for customers never counts.
How a run goes
The five steps of the skill, in order. A change with nothing for customers stops at step two.
- Impact note first. One line before any article is opened: "Help center impact: NONE", or what changed for a user in plain words.
- Classify, abstain first. One change class. Internal, visual-only, marketing-site and bug fixes that restore documented behaviour stop here with a logged no-op.
- Quote the sentence. An article changes only if the agent can quote a sentence that is now wrong, or name something a reader now needs. "Related" is not enough.
- Full rewrite to Changes. Only finished update or create drafts reach the inbox, one entry per PR. At most two verify notes go to the freshness list instead.
- A person decides. Accept, edit or reject with a reason. On accept the article gets a new version and the public page shows Verified today.
Read the skill's SKILL.md
What leaves the machine, and what never does
Sent to Helprism by the agent skill: the one-line impact note, the change class and its reason; the finished article drafts, with the ids of the articles they change; the file paths the change touched, and the ref label a reviewer sees, such as PR #27. By the GitHub App and CLI: changed file paths and the commit messages; the PR title and description, fenced code stripped.
Never sent, never stored: the diff (the agent reads it locally; the CLI never runs git diff or git show); file contents or source code, from any door; patches from GitHub (the App reduces its file listings to paths inside the request); a GitHub token (Helprism stores the installation id, not a token). The intake refuses any body that looks like code: diff, patch or content keys, multi-line paths, diff-shaped text. It answers 400 Helprism never accepts code. Security and data handling.
The Changes inbox
The review unit is the pull request. Each proposed change shows as a rendered preview with added text highlighted and removed text struck through, or as a Markdown diff. Accept all, Accept, Edit, or Reject with a one-click reason. Nothing publishes without an accept, and an accept never takes a live article offline. From the terminal: list_suggestions, resolve_suggestion.
The stamp is the proof
Every public article, widget article and AI answer citation shows Verified {date} beside Last updated, only while the article was verified in the last 90 days. Readers never see a PR number or a commit. An article that was never verified shows nothing: a public page never carries a negative claim.
Before you set it up
Is Helprism sync production-ready?
It is a beta. Expect some missed updates and the occasional false alarm. Every suggestion waits for a person in the Changes inbox, so a wrong draft never reaches your customers.
Which plans include sync?
The agent door (the helprism-sync skill through the MCP server) is on Pro and Business and is never capped. The GitHub App and the CLI are optional server-side doors on Business, capped at 500 events a month; a change with nothing for customers never counts.
Does Helprism see my code?
No. The agent reads the diff on your machine and sends finished drafts and file paths. The GitHub App and the CLI send file paths and commit messages. The intake refuses any body that looks like code.
Can sync publish without a person?
No. Suggestions land in the Changes inbox, and a person accepts, edits or rejects each one. An accept never takes a live article offline.