Connect
Connect your GitHub repository.
Codebase intelligence
See the sequence.
Turn your codebase into a living visual map. Follow changes from commit to impact — and eventually from execution to agent action.
Works with your existing Git workflow.
sequoia/
services/
payment
main
100%
8f31d2Add payment retry handling
main · a3f9c1
3 commits ahead
+128 −14
6 files changed
The problem
A Git diff shows the change.
Seequence shows the sequence.
A diff tells you what lines moved. It doesn't tell you which services, queues, or tests that change reaches — or in what order.
Text diff
14 async charge(order: Order) {
15 const res = await this.gateway.charge(order);
16- return res;
16+ if (!res.ok) {
17+ this.retryCount++;
18+ scheduleRetry(order);
19+ }
20+ return res;
21 }
// 1 file changed, 5 insertions(+), 1 deletion(-)
System context
PR #481
Add payment retry handling
- PaymentServicechanged
- RetryManagerdirect
- PaymentQueuedownstream
- Workerdownstream
- PaymentWebhookconsumer
- payment.spec.tstests
How it works
From code to context.
Three steps turn a repository into a map you can trace.
Map
See the structure and relationships inside your system.
Trace
Follow every important change through the codebase.
GitHub
Code Graph
Commit
Impact
Product
See how your software works, changes, and evolves.
FEATURE 01
Understand the system
Start at the system level. Drill down only when you need the detail — from repository, to services, to modules, files, and functions.
Semantic zoom keeps the context while you descend.
sequoia / payment
Focus modeFit
sequoiarepo
services4 services
payment12 files
payment.service.tschanged
retry.manager.tsnew
systemfunction
FEATURE 02
See what changed
Scrub through commits and watch the graph transform. Select a version to see exactly what appeared, changed, or disappeared between states.
Compare states, not just lines.
commits / payment
Compare commits
v145 — Worker added downstream of PaymentQueue.
FEATURE 03
Follow the impact
From the node you changed, follow the path outward: direct dependencies, then downstream consumers, then the tests that guard them.
Trace the change.
impact / payment.service.ts
PaymentServicechanged
RetryManagerdirect
PaymentQueue · Workerdownstream
payment.spec.ts · retry.spec.tsaffected tests
FEATURE 04
Review PRs visually
Open a pull request with the whole system in view. See which services it touches, what it depends on, and which tests stand between the change and main.
See what a pull request means in system context.
pull / 492
Focus modeShow impact
PR #492
Refactor authentication
12
files changed
4
modules touched
2
services affected
5
related tests
auth/session.ts+64 −22
auth/token.manager.ts+31 −8
gateway/routes.ts+12 −12
FEATURE 05
See the future of software tracing
Eventually, trace more than code. Seequence is being built to trace runtime behavior and AI-agent workflows alongside your codebase.
Clearly labeled — this is the direction, not a shipped feature.
Roadmap
User request
Agent
Planner
Tool
Repository
Edit
Tests
Commit
Use cases
Where the map pays off.
ONBOARDING
Understand an unfamiliar repository faster.
CODE REVIEW
See what a pull request means in system context.
REFACTORING
Trace dependencies before changing architecture.
AI-GENERATED CODE
Understand what your coding agents changed — and where those changes travel.
The living codebase
Your codebase isn't static. Your map shouldn't be either.
Every commit reshapes the graph. Watch the same system evolve across a week — nodes join, merge, reconnect, and retire.
rev v142 · Monday
Order flow mapped
The core order path is traced: gateway to order to payment to the queue.
added this commit
changed this commit
removed this commit
Security
Your code is yours.
Seequence is built to read your repositories with the least access it needs — and to make that access visible and revocable.
Private repositories
Connect private repos without exposing them publicly or to other workspaces.
Encrypted connections
Traffic to GitHub and between services uses TLS in transit.
Granular GitHub permissions
Request only the scopes a feature needs, and review them before you approve.
Source-code handling transparency
Know what is read, what is stored, and for how long — documented in plain language.
Data deletion controls
Disconnect a repository and remove its indexed data from your workspace at any time.
Transparency note
Seequence reads repository structure and history through the GitHub API and your installed app permissions. We do not claim certifications we have not earned — as compliance milestones are reached, they will be listed here with their scope and date.