Skip to content
A two-node SWEny workflow, survey then explain, beside the receipt ticket its run prints, stamped ENV SCOPED and SANDBOXED.

SWEny

Workflows for coding agents. One set of rules, a receipt for every run.
Terminal window
npm install -g @sweny-ai/core

SWEny runs nodes on Claude Code by default; Codex is shipped and pi and ACP agents are experimental (see Agents and policies). For Claude Code you need an Anthropic API key, OAuth token, or an authenticated Claude Code instance.

Terminal window
sweny workflow create "scan our repo for security issues, check dependencies \
for vulnerabilities, and create Linear tickets for anything critical"
GitHub Security Audit
┌─────────────────────────────────┐
│ ○ Scan Commits for Secrets │
└───────────────┬─────────────────┘
│
┌───────────────▼─────────────────┐
│ ○ Scan Deps for Vulnerabilities │
└───────────────┬─────────────────┘
│
┌───────────────▼─────────────────┐
│ ○ Compile Security Report │
└───────────────┬─────────────────┘
│
┌───────────────▼─────────────────┐
│ ○ Create Linear Tickets │
└─────────────────────────────────┘
Save to security_audit.yml? [Y/n/refine]
Terminal window
sweny workflow run .sweny/workflows/github_security_audit.yml

One sentence in, a workflow YAML out. You review it before it runs.

Don’t like the result? Edit it the same way you created it:

Terminal window
sweny workflow edit security_audit.yml "add a quality gate that rejects \
vague findings, and loop back to re-scan if rejected"

SWEny ships two built-in workflows you can run immediately:

Triage

Monitors your observability platform for errors, investigates root causes, creates issues, writes fixes, and opens PRs, automatically. Learn more

Implement

Takes an existing issue, analyzes the codebase, writes a fix, opens a PR, and notifies your team. Trigger it manually or chain it from Triage. Learn more

Terminal window
sweny triage --dry-run # investigate production errors
sweny implement ENG-123 # fix a tracked issue and open a PR

Or build your own from a single sentence with sweny workflow create.

Generate AI-driven end-to-end tests for any web app, no test scripts to write:

Terminal window
sweny new e2e # wizard asks about your flows → generates workflow YAML
sweny workflow run # AI agent drives a real browser to test your app

The wizard supports 7 flow types: registration, login, purchase, onboarding, upgrade, cancellation, and custom. Each generates a self-contained workflow with auto-generated test credentials and optional cleanup. Get started with E2E testing

SWEny workflows aren’t limited to triage and fixes. They can also drive data extraction, research, and quality-gated pipelines.

Data Pipelines

Turn unstructured documents into structured data with LLM extraction, automated quality gates, and change detection. Read the deep-dive

Security Reviews

Ingest vendor questionnaires, draft answers from your security posture docs, and validate nothing is overstated.

Deploy any workflow to GitHub Actions with three secrets and a cron schedule. SWEny monitors your production errors and opens fix PRs while you sleep.

.github/workflows/sweny-triage.yml
- uses: swenyai/triage@v1
with:
claude-oauth-token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
observability-provider: sentry
sentry-auth-token: ${{ secrets.SENTRY_AUTH_TOKEN }}

Full Action guide: setup, scheduling, and service maps.

Install the Claude Code plugin and get slash commands, MCP tools, and a startup hook, without leaving your conversation:

/plugin marketplace add swenyai/sweny
/plugin install sweny@sweny-official

Then type /sweny:triage, /sweny:implement ENG-123, /sweny:e2e-run, or any of the 9 available commands. Claude can also autonomously delegate tasks to SWEny’s DAG executor via MCP tools.

SWEny connects to the tools you already use (GitHub, Linear, Sentry, Datadog, BetterStack, Slack, and more) through built-in skills and MCP servers. Set an API key and the skill is ready. Bring your own MCP servers to connect anything else.

Studio is a visual DAG editor. Run it from a repo checkout with npm run dev -w @sweny-ai/studio. Live mode connects to a WebSocket or SSE event URL you provide and overlays node state as events arrive.