Skip to main content
The Content Agent settings live in Content Agent → Settings, grouped into three cards: Automation, schedule, and publishing. Schedule and publishing also appear in the setup wizard on first run; enable and budget share live only in Settings. Saving requires at least one enabled publish day.

​
Automation

  • Enable Content Agent: the master switch. Off pauses planning and generation without losing your configuration; drafts already in review stay reviewable. You can’t enable it until the setup wizard has been completed once.
  • Budget share (default 90%): the slice of your organization’s content generation allowance the agent may spend this billing period; the rest stays reserved for manual drafts in Create Content and Optimize Content. The meter above the slider shows four segments: Used (generated this period), Queued (planned pieces that will consume budget when they generate), Available, and Manual drafts (held back for you). You can’t lower the share below what’s already committed to queued work, so lowering it never strands scheduled pieces.
When the agent’s share runs out, generation pauses. Raise the share if organization capacity remains, or wait for the period reset. When the whole organization allowance is used, manual generation pauses too. The Content tab shows a notice with the reset date in both cases. The Promptwatch Content Agent Automation settings card with the enable switch, generation budget meter, and budget share slider.

​
Choose when to publish

  • Schedule timezone: the IANA timezone your publish days and hours are interpreted in. It defaults to your organization timezone and is independent of your browser timezone, so a team in three countries publishes on one clock.
  • Publishing days & hours (default: every day, 09:00 to 18:00): a per-weekday grid of allowed publish windows. Days switched off never publish; at least one day must stay enabled. The agent picks a specific time inside the window for each piece; the reason for that time is on the Activity run for the piece.
Blackout dates (specific dates when publishing is blocked, for example a product launch week) exist in the configuration and can be set through the API and MCP tools, but are not yet editable in the dashboard.

​
Decide how it publishes

  • Autonomy mode: Review first routes every draft through your review inbox, and nothing publishes without an accept. Auto-publish lets drafts that pass the quality checks skip the inbox and publish at their slot, labeled “Auto-approved”. On first run the setup wizard preselects Auto-publish. See Reviewing drafts.
  • Publish state: whether approved content is pushed to your CMS as a draft (you press the final publish button in the CMS) or published live directly. The setup wizard preselects Publish live; a CMS draft still needs a final publish in the CMS, even in Auto-publish mode.
  • CMS Integration (default: manual export): the connection content is pushed to. Webflow and Framer connections are supported (WordPress is available on request); connections are created under CMS Integrations, then selected here. Manual export means no push: you copy the content out and publish it yourself, then record the URL. See Publishing and tracking results.
The Promptwatch Content Agent publishing settings card with CMS integration, Review first versus Auto-publish, and publish-live versus draft cards. Publish timing (default: at scheduled slot) and max per day (default: 1, up to 20) also exist on the configuration and, like blackout dates, can be set through the API and MCP tools but are not yet editable in Settings.

​
Settings that live elsewhere

The writer’s defaults are project-wide, not agent-specific, so they live in Brand Book → AI Agent: content language, tone of voice, default tools (web search, internal links, image generation, Knowledge Base search, and others), image style, blocked words, and the default author. The Content Agent applies them to every automated piece unless the planner set piece-specific options, and manual generation uses the same defaults.