Open-source security workflows in your browser or coding agent.
Backed by Y Combinator · The Swiss Applied AI & Cybersecurity Research Lab
0.security ·
Documentation ·
FoxGuard
Get started
Install on Apple Silicon macOS or x64/ARM64 Linux:
curl -fsSL https://raw.githubusercontent.com/0sec-labs/0/main/install.sh | bash export PATH="$HOME/.0/bin:$PATH" 0 web
Command Center (browser): 0 web · Terminal: 0
Configure a model provider before running AI workflows.
Workflows
Browser, CLI, and MCP share one workflow runner with retained results.
Findings are prioritized by business impact: affected customers and data, fraud, critical services, and disruption. Each priority includes a rationale; missing context stays Not assessed. CVSS remains available as technical severity.
| Work | Built-in templates |
|---|---|
| Assess | Repositories, dependencies, APIs, web configuration, scoped penetration tests, package behavior, smart contracts, native code |
| Verify | Findings with replay evidence |
| Fix | Candidates with regression tests |
| Research | Security research, deep source investigation |
Start from 12 templates, customize steps, and run manually or with browser triggers and schedules. Template: starting point · Workflow: reusable steps · Run: one execution.
Learning retains local run activity, source-grounded notes and evaluated
improvement history. Saved workflows keep immutable revisions and support restore.
Use 0 learning status or open Learning in the browser.
Learning documentation.
0 workflow list --templates
0 workflow run --template security-research \
--target /absolute/path/to/repo --workspace /absolute/path/to/repo \
--format json > run.json
0 runs listWorkflow guide: inputs, limits, and results.
See Zero at work
A source review of the included demo API, with code locations and suggested fixes.
Start a workflow from a template and edit its steps.
Use 0 from another agent
Use the CLI commands above, or MCP to discover templates, create workflows, and manage runs:
0 mcp-server --workflows --workspace /absolute/path/to/repo
Local MCP requires an explicitly selected host-local execution profile.
For a registered remote engine, use 0 mcp-server --workflows --backend production.
0's model provider is separate from the connecting agent's session.
Browser chat's Connect an external agent copies a setup prompt. CLI and MCP workflow clients automatically attach to a running local web engine for the same workspace and control database. To attach explicitly to the sessions and runs already open in an engine:
0 mcp-server --workflows --engine-url http://127.0.0.1:3000 \ --engine-token-env ENGINE_TOKEN --session SESSION_ID 0 sessions list --engine-url http://127.0.0.1:3000 --engine-token-env ENGINE_TOKEN
Set ENGINE_TOKEN to the engine's configured bearer credential. Attached clients
share the browser's session and run lifecycle; disconnecting leaves the engine
running. Omit --session to create a session under the engine's admission grants.
See MCP setup and individual tools or local and remote engines.
Plugins
Connect GitHub, Elastic, Semgrep, Snyk, Linear, Jira, Cloudflare, Slack, and Teams through plugins and MCP.
More guides: installation · GitHub Actions · plugin development · troubleshooting.
Development
Install dependencies, run npm run dev, and open the printed browser address.
See CONTRIBUTING.md.
Status and safety
Research preview. Assess authorized systems and review findings and fixes.
Run 0 or 0 web to open the browser console without an account.
The interactive terminal UI is retired; headless CLI, automation, MCP and binary commands remain available.
Use 0 chat --prompt "your request" for one-shot automation; set --mode standard for explicit scope checks.
The optional scope plugin enforces target boundaries.
Report vulnerabilities through SECURITY.md. Licensed under MIT OR Apache-2.0.
Public disclosures and upstream fixes. Thanks to OpenTUI, Bun, React, Models.dev, LiteLLM, and our contributors.