Local-first AI code review

The engineering trust layer for AI-generated code

Cursor, Claude Code and Codex can write code fast. Sego checks whether that code is safe enough to ship.

The gap AI coding does not close

  • Security Is the code safe? Are there hardcoded secrets?
  • Risk Is there SQL injection or dangerous command execution?
  • Merge Is this PR ready to merge?
  • Diff Did the AI change more than expected?

What Sego does

Review

Structured code review

Reviews staged changes and outputs severity, file, line, evidence, risk, and suggestion for each finding.

Security

Safety lock

Detects hardcoded secrets, dangerous commands, absolute paths, and unexpected file changes.

History

Review artifacts

Every review is saved to .sego/reviews/ as structured JSON and readable Markdown.

Recovery

Crash recovery

Abnormal shutdown is detected on next launch. Resume without replaying old tool calls.

Permissions

review-trust profile

Read-only commands are auto-allowed, dangerous commands are denied, and review workflows need fewer prompts.

Integration

Sidecar skill (PoC)

Early integration for Claude Code, Codex, and Cursor through a sidecar review interface.

See it in action

AI-generated code (app.py):
app.py line 6
CRITICAL: SQL injection
Risk: user input concatenated directly into SQL query
Fix: use parameterized queries

Sego output:
6 findings detected (1 critical, 1 high, 1 medium, 2 low, 1 info)
Artifact saved: .sego/reviews/review-001.json
Status: review complete, 2 issues must be fixed before commit

Looking for the first 20 AI coding users

If you use Cursor, Claude Code, Codex, Copilot or another AI coding tool, send us a small AI-generated project. We will run a free Sego review and send back a structured report.

Temporary launch intake uses GitHub Issues while the public form is being prepared. Overseas paid audits use BNB Chain after scope confirmation. Do not include secrets, credentials, or private customer data in public issues.