격리된 git worktree, 자동화된 품질 게이트, 근거 기반 PR 생성을 통해 AI 코딩 에이전트가 GitHub issue를 해결하도록 오케스트레이션합니다.
다른 이름 sequant-io/sequant
- 스타
- 1
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 13일
- 라이선스
- MIT
Sequant MCP란?
Sequant은(는) MCP server입니다. 격리된 git worktree, 자동화된 품질 게이트, 근거 기반 PR 생성을 통해 AI 코딩 에이전트가 GitHub issue를 해결하도록 오케스트레이션합니다.
프로젝트 README에서 생성된 요약
Sequant MCP server 정보
Sequant는 AI 코딩 에이전트가 다단계 워크플로우를 통해 GitHub issue를 해결할 수 있는 구조화된 프레임워크를 제공합니다. 계획 단계부터 구현, 그리고 최종 리뷰 단계로 이어지는 이 프로세스는 격리된 git worktree를 사용하여 하나의 issue 작업이 메인 브랜치를 오염시키거나 다른 작업에 간섭하지 않도록 보장합니다. 이러한 방식을 통해 개발자는 저장소 상태를 깨끗하게 유지하면서 여러 issue를 동시에 처리할 수 있습니다.
Claude Code 또는 Aider를 사용하는 개발자를 위해 설계되었으며, 대화형 CLI 내의 플러그인 또는 CI 환경을 위한 headless npm 패키지 형태로 작동합니다. 실행을 위해 GitHub CLI와 Git이 필요합니다. 이 도구는 Node.js 및 TypeScript 프로젝트에 최적화되어 있지만, 기반이 되는 worktree 메커니즘은 언어에 구애받지 않습니다.
이 MCP server의 차별점은 검증 가능한 결과에 중점을 둔다는 것입니다. 에이전트는 단순히 코드를 작성하는 것에 그치지 않고, 타입 안정성 검사, 보안 스캔, Semgrep 정적 분석을 포함한 자동화된 품질 게이트를 통과해야 합니다. 모든 pull request에는 각 수락 기준이 어떻게 충족되었는지 보여주는 근거가 포함되어 있어, 최종 병합 권한을 인간 개발자가 유지할 수 있도록 합니다.
활용 사례
- 1자동화된 issue 해결AI 에이전트가 GitHub issue의 초기 설명부터 완료된 pull request 생성까지 수행하도록 지시합니다.
- 2검증 가능한 코드 품질에이전트가 작성한 모든 코드가 특정 수락 기준에 따라 검사되었는지 확인합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Sequant MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Sequant MCP 설치
$ claude mcp add sequant -- npx -y sequantCursor에 Sequant MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"sequant": {
"command": "npx",
"args": [
"-y",
"sequant"
]
}
}
}VS Code에 Sequant MCP 설치
.vscode/mcp.json
{
"servers": {
"sequant": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sequant"
]
}
}
}VS Code CLI에 Sequant MCP 설치
$ code --add-mcp '{"name":"sequant","type":"stdio","command":"npx","args":["-y","sequant"]}'Claude Desktop에 Sequant MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"sequant": {
"command": "npx",
"args": [
"-y",
"sequant"
]
}
}
}Codex에 Sequant MCP 설치
$ codex mcp add sequant -- npx -y sequantCodex config.toml에 Sequant MCP 설치
~/.codex/config.toml
[mcp_servers.sequant] command = "npx" args = ["-y", "sequant"]
Gemini CLI에 Sequant MCP 설치
$ gemini mcp add -s user sequant npx -- -y sequantGemini settings.json에 Sequant MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"sequant": {
"command": "npx",
"args": [
"-y",
"sequant"
]
}
}
}자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능sequant-io/sequant is public and reachablegithub.com/sequant-io/sequant ↗통과
- 패키지가 이 저장소를 소스로 명시sequant names sequant-io/sequant as sourcenpmjs.com/package/sequant ↗통과
- 빌드 출처(Sigstore 증명)No build attestation published for this release검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-12github.com/sequant-io/sequant ↗통과
- OpenSSF ScorecardOpenSSF Scorecard 5.9 / 10; weakest: Code-Review 0, Token-Permissions 0, CII-Best-Practices 0scorecard.dev/viewer/?uri=github.com/sequant-io/sequant ↗부분 9/15
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from sequant통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기Sequant
AI coding agents that prove their work — each acceptance criterion checked, and you hold the merge button.
For developers who won't merge what they can't trust — solo or on a team.
Sequant takes a GitHub issue to a merge-ready PR through three phases — plan, implement, review — each in its own git worktree, with quality gates between them. The PR arrives with evidence: every acceptance criterion re-checked against the code and posted to the issue. On a held-out fixture with 5 planted defects, the review named all 5 in each of 3 runs (measured). The merge is always yours.
sequant.io — docs, guides, and getting started.
Why Sequant
- Stop babysitting the agent. AI coding agents write code well and leave the workflow to you — planning, isolation, review, merge safety. One command runs the whole issue → PR path, not just the coding step.
- You stay in control.
sequant runstops at the PR and never merges. That is an invariant, not a setting. (The/fullsolveskill merges only when you opt in:--auto-merge,run.autoMerge: truein settings, or asking it to merge.)
Works with Claude Code (default) or Aider, on any git repository with GitHub issues. Tuned for Node.js/TypeScript projects; the worktree workflow is language-agnostic.
Quick Start
Prerequisites
- An AI coding agent: Claude Code (recommended ≥ 2.1.288) or Aider via
--agent aider. Experimental: Codex via--agent codex, opencode via--agent opencode— read their notes before relying on either. - GitHub CLI (
gh auth login) and Git. - Node.js 22.13+ — for the npm/CLI install path only.
- Optional MCP servers:
chrome-devtools(browser tests via/test),sequential-thinking,context7.
Why Claude Code ≥ 2.1.288? Sequant's pre-tool hooks lean on Claude Code's native dangerous-
rmanalyzer, which fires even underbypassPermissions. Its command-substitution coverage (e.g.echo "$(rm -rf ~)") landed in 2.1.208, and its coverage ofbash -c/sh -cscripts (e.g.bash -c "rm -rf ~") landed in 2.1.288. On an older version, a phase agent runningbash -c "rm -rf ~"is not stopped by either side. Plugins cannot declare a minimum Claude Code version, so this is a recommendation, not an enforced floor.
Phase agents run the bundled Claude Code.
sequant runphases go through the Agent SDKquery()and use the Claude Code bundled with@anthropic-ai/claude-agent-sdk(2.1.296 at SDK 0.3.296), not theclaudeyou installed, so the two versions can differ. The recommended version above is for your interactive CLI. Inside a phase agent, thermanalyzer coverage it describes comes from the bundled version, which is already past 2.1.288.
Install
Pick the path that matches where you run Sequant:
Inside Claude Code (plugin) — skills, hooks, and MCP tools, no npm required:
/plugin marketplace add sequant-io/sequant
/plugin install sequant@sequant
/sequant:setup
Plugins do not auto-update. Claude Code pins a plugin to the version you installed and never updates it on its own — even as new releases ship. To pick up a new version, run
claude plugin update sequant@sequant, then restart Claude Code. Sequant's pre-tool hook warns once a day when your installed version falls behind the marketplace.
sequant runalso needs.claude/skills/{spec,exec,qa}committed to the repo, along with.claude/skills/_shared(the references those skills link to)./sequant:setupcopies them from the plugin into.claude/skills/and prints a reminder to commit them — do that before your firstsequant run. Without npm/npx available,sequant syncis not an option for a plugin-only setup; re-run/sequant:setupif the directory is ever missing.
Headless / CI (npm package) — drive runs from the terminal or a CI job:
npm install sequant # or: pnpm add / yarn add / bun add sequant
npx sequant init # install skills into your project
npx sequant doctor # verify setup
Commit
.claude/skills/. It is a runtime dependency, not a cache:sequant runphase agents load skills from that directory only, so a checkout (or cleanup) that drops it breaks every run.sequant runpre-flights the directory and fails fast with the fix (sequant sync --only skills) if it is missing.
Your first run
Inside Claude Code, solve an issue end-to-end:
/fullsolve 123
Or headless from the terminal (-Q runs the quality loop):
npx sequant run 123 -Q
Either way, Sequant creates an isolated worktree, posts a plan comment to the issue, and opens a merge-ready PR.
What a run looks like
A real /fullsolve 683 (the run that built sequant ready itself):
SEQUANT WORKFLOW · #683
spec ✔ 9 ACs extracted · plan posted to the issue
exec ✔ 29 tests + docs + lint fix · committed to the feature branch
qa ✔ full build + suite · 8/9 ACs MET · 1 manual AC marked PENDING (not faked)
pr ✔ opened #686 · 7/7 checks green · MERGEABLE
→ stops at the human merge gate · never auto-merges · run `merge` to land it
QA findings post back to the issue as comments, with each acceptance criterion re-checked independently.
What's new in 2.20
- The PR says what QA did and didn't do — until QA has reviewed the latest exec, the PR body says
QA has not run. After QA it shows the latest verdict, exec's## Summarywith its mutation records, and a## Follow-upschecklist of everything QA deferred. See What the PR body carries. - QA closes its own loose ends — every deferred item must end
filed #N,fixed in this PRordropped: <reason>. An unresolved item keeps the verdict belowREADY_FOR_MERGE. - Failures are recorded, not just printed — a
SPEC_DIVERGENCEor repeated-refusal halt is recorded in the run log, the state and the MCP result. A failedghcomment or label post is now an error, not a silent success. - Recommended Claude Code is now ≥ 2.1.288 — older versions don't stop a phase agent running
bash -c "rm -rf ~". See Prerequisites. - Narrower skill permissions — skills no longer pre-approve broad shell,
gh api,rmorfindaccess. When you run a skill by hand, those commands now ask first;sequant runis unaffected.
Since 2.17, every release soaks on the next tag against a downstream canary — a real install of the previous minor, driven through sync, init, update and doctor by the new build — before it is promoted to latest.
Full history: CHANGELOG · Migrating from v1.x
How It Works
Sequant enforces a structured workflow through slash commands (interactive) or CLI (headless):
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
│ /spec │───▶│ /exec │───▶│ /test │───▶│ /qa │───▶ Merge
└─────────┘ └─────────┘ └─────────┘ └─────────┘
│ │ │ │
▼ ▼ ▼ ▼
Plan Build Verify (UI) Review
/testis optional — used for UI features when Chrome DevTools MCP is available.
Worktree Isolation
Sequant uses Git worktrees to isolate each issue's work:
your-project/ # Main repo (stays on main branch)
../worktrees/
feature/
123-add-login/ # Issue #123 worktree (feature branch)
456-fix-bug/ # Issue #456 worktree (feature branch)
Why worktrees?
- Work on multiple issues simultaneously
- Never pollute your main branch
- Each issue has its own dependencies and build
- Safe to discard failed experiments
Agent Contract
Every project gets .claude/memory/constitution.md — the machine-enforceable agent contract that answers "what will the agent refuse to do, what must every PR satisfy, and where does it stop for me?":
- Definition of Done — generated from
/qa's §7 gate list; a CI check (lint:constitution-dod) fails when the table drifts from the live gates. These are project-wide — issue ACs don't restate them. - AC Authoring Standard — the house format for writing ACs (single-line,
Evidence:/Risk:/Human decisionfields, Non-Goals); referenced by/spec's lint warnings. - Boundaries — every rule names its enforcer: the force-push hook, the worktree-only editing guard, the mutation-verification gate.
- Budgets & Stop Conditions — iteration caps, the human merge gate, hold states, and gap-prompt discipline.
The file's declared ownership policy is user-owned: plain sequant update and sync preserve your edits. Only --force replaces it.
AGENTS.md ownership. Every AGENTS.md sequant generates starts with a marker line, <!-- sequant:agents-md v=<version> h=<sha1> -->, whose hash covers the rest of the file. sync only regenerates the file when that marker is present and its hash still matches the body — otherwise the file is treated as user-owned (hand-edited, or written before the marker existed) and is left byte-identical, reported as preserved, and only replaced with sync --force. Use sync --no-agents-md to skip AGENTS.md entirely. (update has no AGENTS.md awareness — unaffected.)
scripts/dev links and --dry-run. The scripts/dev/*.sh links point at your project's own node_modules/sequant/templates/scripts/ whenever it exists, so a fresh clone plus npm install keeps them working; a templates directory under an npx cache or outside the project tree yields copies instead, with one line saying why. sync --dry-run and update --dry-run list exactly the paths the apply step writes — the AGENTS.md decision, each link whose target would change (sync only: update leaves scripts/dev links to sync and names any that are out of date), and the opencode shim (refreshed only on projects that opted in with --agent opencode, and only when it drifted). No writer follows a symlink: a link at any sequant-written destination, .mcp.json included, is replaced and its target left untouched, and a directory where a file belongs is reported as <path> is a directory; move it aside and skipped.
Quality Gates
Every /qa runs automated checks:
- AC Adherence — Code verified against acceptance criteria
- Type Safety — Detects
any,as any, missing types - Security Scans — OWASP-style vulnerability detection
- Semgrep Static Analysis — Stack-aware rulesets, custom rules via
.sequant/semgrep-rules.yaml - Scope Analysis — Flags changes outside issue scope
- Execution Evidence — Scripts/CLI must pass smoke tests
- Test Quality — Validates test coverage and mock hygiene
- Anti-Pattern Detection — Catches N+1 queries, empty catch blocks, stale dependencies
When checks fail, /loop automatically fixes and re-runs (up to 3x).
Thinking of building this on a graph framework?
You could assemble this workflow yourself on LangGraph, CrewAI, Mastra, or the Claude Agent SDK — they sell the primitives and leave the workflow as an exercise. Sequant is the finished, hardened version of what you'd end up building, in the frameworks' own vocabulary:
- Isolated execution — one git worktree per issue, resolved by the branch git reports rather than directory globs
- Human-in-the-loop approval gate —
sequant runstops at the PR and never merges; this is an invariant, not optional wiring (/fullsolvemerges only on an explicit opt-in:--auto-merge,run.autoMerge: true, or a direct request) - Guardrails — QA verdicts with an enforced floor, mutation-verified gate tests, scope and security checks
- Durable execution — a rate-limit halt writes a resumable record;
sequant resumepicks up where it left off, skipping completed phases - State management — per-issue and checkout-scoped locks, so concurrent sessions can't interleave git operations in the same tree
- Deterministic control flow — a line starting
Depends on: #Nqueues an issue behind the one it needs, and--sequentialruns a batch one issue at a time (see Write Issues Sequant Can Execute)
On a general framework, every one of these is something you wire up — and can wire wrong or skip. Here they hold for every run. The boring 80% (retries, resume, locking, exit codes your scripts can trust) has already been run in anger; the CHANGELOG is the receipts.
Using Sequant
Solve one issue (the 80% path)
The most common invocation — no flags. Auto-creates a worktree, posts a plan comment to the issue, and opens a PR.
In Claude Code:
/fullsolve 123
Headless (-Q runs the quality loop):
npx sequant run 123 -Q
sequant run --helpis the authoritative flag list. There is no--skip-spec— to skip the plan phase, use--phases exec,qa.
Batch: triage, then run
For several issues at once, the ritual is /assess → paste the commands it emits:
/assess 101 102 103
/assess returns a dashboard (PROCEED / PARK / CLOSE per issue), dependency ordering, and ready-to-paste commands like npx sequant run 101 -Q. The quality loop (-Q) is part of every command it generates.
From Claude Code, via the MCP server
With the plugin installed, drive runs through the MCP server from inside Claude Code:
use sequant plugin to fullsolve 123
You get back a structured phase-timing table and verdict. The same tools — sequant_run, sequant_status, sequant_logs — are available to any MCP client; npx sequant serve exposes them headlessly.
QA on the issue
Re-verify a resolved issue or PR. Findings land as issue comments, with each acceptance criterion independently re-checked:
123 any gaps? # re-QA issue #123
/qa pr488 # re-QA a PR
Upgrade without surprises
You keep your own AGENTS.md and a customized constitution. A new sequant version should not eat either — so look before it writes:
$ npx sequant sync --dry-run
AGENTS.md: preserved
Summary (dry-run):
New files: 1
Modified: 3
Customizable (preserved): 1
(dry-run mode - no changes made)
preserved means user-owned: sync leaves it byte-identical until you run sync --force once. Exit code 1 means there is work to apply, so a CI job can gate on the preview.
Merge
merge # squash-merge + sync main + worktree cleanup + post-merge build/test
Command Reference
Most work goes through a handful of top-level commands. The rest are either pipeline internals (run for you) or occasional tools.
Everyday
| Command | What it does |
|---|---|
/fullsolve <issue> |
Complete spec → exec → qa pipeline; opens a PR. The 80% path. |
/assess <issues…> |
Triage one or more issues; emits a dashboard + ready-to-paste run commands (6-action vocabulary). |
npx sequant run <issues…> |
Headless equivalent of /fullsolve; batches run in parallel. Add -Q for the quality loop. |
/qa <issue> |
Code review + quality gate; posts findings as issue comments. |
npx sequant merge <issues…> |
Batch integration QA before merging. Add --watch to wait for each PR's CI checks to finish (configurable --interval/--timeout), then run the checks and report — it never merges. |
Pipeline internals
/spec, /exec, /loop, /testgen, /test are the phases that /fullsolve and sequant run orchestrate for you. You can invoke them directly, but rarely need to.
Occasional / advanced
| Command | What it does |
|---|---|
sequant ready <issue> |
Post-resolve full-weight A+ QA gate; drives to merge-readiness, then stops at the human merge gate (never merges). |
sequant resume |
Re-enter runs halted on a rate-limit window once it reopens; no-op before resumeAt, so it is safe to schedule via cron/launchd. See halt-and-resume.md. |
/merger |
Multi-issue merge coordination. |
/improve |
Codebase analysis and improvement discovery. |
/security-review |
Deep security analysis. |
/verify |
CLI/script execution verification. Needs an issue number; a bare /verify (such as Claude Code's pre-commit nudge) is a no-op. |
/docs · /clean · /reflect |
Feature docs, repo cleanup, workflow reflection. |
CLI utilities
npx sequant init # initialize in project
npx sequant update # update skill templates
npx sequant doctor # check installation
npx sequant status # show version and config
npx sequant state <cmd> # manage workflow state (init/rebuild/clean)
npx sequant locks <cmd> # inspect/clear per-issue concurrency locks
npx sequant stats # local workflow analytics (cohort filter: --label / --since)
npx sequant dashboard # real-time workflow dashboard
npx sequant serve # expose workflow tools over MCP
See Run Command Options, Merge Command, State Command, and Analytics for details.
Concurrency
Multi-issue runs are parallel by default, and a per-issue lock (.sequant/locks/<issue>.lock) stops two sessions from clobbering the same issue — see Concurrency & Per-Issue Locks for stale recovery, takeover (--force), and sequant locks subcommands.
Configuration
// .sequant/settings.json
{
"run": {
"qualityLoop": false,
"maxIterations": 3,
"defaultBase": "feature/dashboard", // Optional: custom default base branch
"phases": {
"exec": { "model": "sonnet", "effort": "medium" } // Optional: per-phase model/effort override
}
}
}
See Customization Guide for all options, Per-Phase Model & Effort for the run.phases shape, the --models/--efforts flags and precedence, and Spec-Divergence and Repeat Halts for the SPEC_DIVERGENCE and AC_NOT_MET_REPEATED halts.
Platform Support
| Platform | Status |
|---|---|
| macOS | ✅ Full support |
| Linux | ✅ Full support |
| Windows WSL | ✅ Full support |
| Windows Native | ⚠️ CLI only |
Documentation
- Quickstart — 5-minute guide
- Complete Workflow — Full workflow including post-QA patterns
- Getting Started
- What We've Built — Comprehensive project overview
- What Is Sequant — Elevator pitch, pipeline diagram, architecture
- Workflow Concepts
- Run Command
- Concurrency & Per-Issue Locks
- Spec-Divergence and Repeat Halts —
SPEC_DIVERGENCE,AC_NOT_MET_REPEATED, and the evidence bundle - Plugin Eval CI — manual-dispatch
claude plugin evalworkflow, budget cap, and canary design - Git Workflows
- Customization
- Troubleshooting
- Threat Model — untrusted-input surfaces, which defenses hold when the model is compromised, OWASP Agentic Top 10 mapping · Security Policy — reporting a vulnerability
Stack guides: Next.js · Rust · Python · Go
Feedback & Contributing
Reporting Issues
- Bug reports: Bug template
- Feature requests: Feature template
- Questions: GitHub Discussions
Using /improve for Feedback
Run /improve in Claude Code to analyze your codebase and create structured issues:
/improve # Analyze entire codebase
/improve security # Focus on security concerns
/improve tests # Find test coverage gaps
The skill will present findings and offer to create GitHub issues automatically.
Contributing
See CONTRIBUTING.md for development setup and guidelines.
Telemetry
Sequant does not collect any usage telemetry. See docs/reference/telemetry.md for details.
License
MIT
Sequant MCP 질문
Sequant MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add sequant -- npx -y sequant를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Sequant MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.