Skip to main content
A content draft is the first version of the content an action asks for, written by an agent from the action’s ready brief. A create action gets a full page in markdown. A refresh action gets section edits: a change list for its existing page. DevTune never publishes a draft. You review it, download it, edit it in your own CMS and publish it yourself. Content drafts are available on every plan. Each run uses agent credits.

​
Generate a draft

  1. Open an action that has a ready brief
  2. In the Draft section below the brief, select Generate draft
  3. Choose a model. The dialog shows its estimated credits per run
  4. Select Generate draft to start the run
The Page Drafter writes a create action’s page. The Section Editor writes a refresh action’s section edits. While the run is going, the section shows Writing draft…. Only one draft runs for an action at a time; drafts for different actions run side by side. You need project management permission to start one. You can also start from Agents: the Page Drafter and Section Editor cards open the Actions queue filtered to the actions each can draft. Generate draft is unavailable when:
  • The action has no ready brief. Generate the brief first
  • The brief was written before the current brief format. Regenerate the brief, then draft
  • A refresh action’s page is locked. Unlock the page to generate section edits

​
What a draft contains

Page draft. The full page in markdown, written from the brief’s structure and its facts list. A product fact the brief does not list is written without its value and marked [Needs source: …]. Section edits. Up to 20 changes to the page as DevTune last crawled it. Each change names an existing section, quotes its current text and gives the proposed text, or adds a new section after a named heading. Each change has a one-line reason. If DevTune has no crawled copy of the page, every change is a new section at the end of the page. Both drafters follow the style notes in your project’s content preferences, unless a note conflicts with the brief. They avoid linking to your configured competitors.

​
Fact check

Every draft is fact-checked before it is saved. DevTune checks each product fact (a price, number, limit, date, plan, integration or capability of your product) against the brief’s facts list, then against your site. Claims about another company’s product are checked against the brief’s external facts. Instructions, examples and opinions are not checked. The agent gets one pass to fix what the check flags. Anything still flagged is highlighted in the draft with its reason: A summary line above the draft says what was checked. Some facts not checked means some sentences could not be checked; Facts not checked means the check did not run. In both cases, verify the facts yourself before you publish.

​
Review and download

  • Select Download markdown to save the draft. The download lists any flagged facts under Facts to verify
  • Select Generate new draft to write a new version. The previous version is kept, and the Draft section lists up to 10 previous versions
  • Select View run to open the agent run behind the draft
Every version is also in the Library as a Content draft, with Search & grounding off, so other agents never treat an unpublished draft as evidence. When you have published the content, select Mark live on the action with the published URL. Its before/after window opens in Results.

​
From Slack, the API and MCP

  • Slack. Ask Dex in a Slack conversation to draft an action. Dex confirms before it starts the run
  • API. GET /api/v2/projects/{projectId}/actions/{actionId}/draft reads the current draft and its versions, with the markdown, change list and fact check. Reading needs actions.read; a POST to the same path starts a run and needs agents.run
  • MCP. devtune_get_action_draft and devtune_start_action_draft do the same. In code mode they are get_action_draft and start_action_draft
Every path runs the same checks as Generate draft: a ready brief, an unlocked page and enough agent credits.