Developers & Integrations

Block Bad Writing Changes Before They Reach Production

The CI Release Airlock connects your pipeline to WriteGust — every prompt or model change runs through the wind tunnel before merge.

Open API DocsRequest Integration
CI cabin · draft under test

Candidate renewal email · prompt v4.2 · gpt-4.1-mini · run #847

PENDING · 2 flags
Release gate

All rules must pass before production deploy.

Run CI Check to pressurize the cabin — failed items surface in GitHub checks, API, CLI, and webhooks.

API

Writing QA endpoints

Run test suites, fetch results, and arm release gates from CI.

POST /v1/runs
Authorization: Bearer wg_live_…
{
  "suite_id": "suite_renewal_v3",
  "prompt_version": "v4.2",
  "model": "gpt-4.1-mini",
  "context": { "account_id": "acct_…" }
}

→ 201 { "run_id": "run_…", "status": "blocked", "flags": ["fact", "tone"] }
CLI

WriteGust command-line workflow

Pin prompt versions and run flight tests from your terminal.

curl -fsSL https://cli.writegust.com/install.sh | sh
writegust login

writegust suites run renewal-email-v3 \
  --prompt prompt-registry/v4.2 \
  --model gpt-4.1-mini \
  --fail-on-regression

writegust airlock connect github --repo acme/support-ai --branch main

Integrations: GitHub · GitLab · CircleCI · Jenkins · Linear · Slack · Zendesk · Intercom

Pressure before production

Ship Writing Systems You Can Defend.

WriteGust is a Writing Flight Lab — wind-tunnel prompts, vane rubrics, and release airlocks so generated text fails in the bay, not in the inbox.