xexaflow
Xexaflow · pre-flight 0.7 · local-first

Ship while you learn.
Learn while it ships.

The local-first cockpit where AI agents build your SaaS — and you learn the architecture of your own codebase while they ship.

Watch the 60s demo
Free during beta · macOS / Linux / Windows
0.87
Codebase ↑ score
1,247
On the waitlist
312
Lessons delivered
● AGENT · build-checkout RUNNING
14:02:14 · plan decompose feature → 4 sub-tasks
14:02:18 · write src/billing/checkout.ts (+82 -3)
14:02:22 · guard domain leak · paused for review
14:02:29 · explain ↳ why Stripe webhook stays in adapter
14:02:34 · apply 3 / 7 patches · test 12/12 ✓
src/billing/checkout.ts+82 −3
13import { CheckoutPort } from "../ports"
14
15export class StripeCheckout implements
16 CheckoutPort {
17 async startSession(input) {
18 return this.stripe.checkout
19 .sessions.create(input)
20 }
21}
+// guard · domain → infra ✓
12 / 12 tests ✓patch · 4 of 7
↳ HUD · briefing · 3 minREADY
Why your Stripe webhook lives in infra/, not in your route handler.
2 min read · 1 diff to inspect · 1 mini-quiz. Pulled from your commit, not a tutorial.
port/adapterside-effectsbilling
3 queued · 2 unreadopen ↗
↳ REPO MAP · live5 PORTS
YOUR REPOauthdbllmstripeui
12 adapters · 3 entry points● in sync
● all systems · nominalHEX SCORE · 0.87FLIGHT · #142 · 62% · 4 of 7 tasksBRIEFING · 3 queuedLAT · 48.86° N
↳ The cockpit

One window. Two flights at once.

The agent ships a feature on the left. The cockpit teaches you what just happened on the right. Same screen. Same loop. No chat thread to lose.

Total visibility
Workflow · build-checkout · run #142
Add Stripe checkout with metered billing
● LIVE
src/billing/checkout.ts+82 −3
13import { CheckoutPort } from "../ports/checkout"
14
15export class StripeCheckout implements CheckoutPort {
16 async startSession(input: SessionInput) {
17 const session = await this.stripe.checkout.sessions.create({
18 mode: "subscription", line_items: input.items,
19 })
20 return { url: session.url, id: session.id }
21 }
22}
AGENT TRACE
14:02:14 · plan decompose feature → 4 sub-tasks
14:02:18 · write src/billing/checkout.ts (+82 -3)
14:02:22 · guard domain leak · paused for review
14:02:29 · explain ↳ why Stripe webhook stays in adapter
14:02:34 · apply 3 / 7 patches · test 12/12 ✓
GUARDS · 3 ACTIVE
domain → infra direction OK
no secrets in source OK
test coverage ≥ 70% WARN
↓ same run · briefing drafted live
↳ briefing · 90s readqueued · ready when you are

Why your Stripe webhook lives in infra/, not in your route handler.

2 min read · 1 diff to inspect · 1 mini-quiz. Pulled from your commit, not a tutorial.

port/adapterside-effectsbilling
2 min
READ
1 diff
INSPECT
1 quiz
OPTIONAL
↳ excerpt
"Notice how " StripeCheckout implements CheckoutPort — your billing logic stays swap-able. Read why this matters before run #143."
// the contract — interchangeable adapter
interface CheckoutPort {
startSession(input): Promise<{ url, id }>
}

Local-first. Your repo never leaves your machine. Bring your own keys (Anthropic, OpenAI, OpenRouter, local Ollama). The trace is yours, replayable, exportable.

See how it flies
How it flies

Three steps, one loop.

You describe. The agent ships. You learn what just happened — without leaving the cockpit.

Operator-first
01
DESCRIBE

Describe a workflow.

« Add Stripe checkout with metered billing. » « Migrate auth to passkeys. » The cockpit parses the intent against your real repo — your patterns, your ports, your conventions — and proposes a flight plan.

↳ ~30 seconds · indexed locally · no cloud upload
02
SHIP

The agent ships it.

Live trace as it writes. Guards pause it at decision points so you can review, approve, override. Every patch is reversible. Every run is replayable. You stay the pilot.

↳ every action observable · every commit reversible
03
LEARN

Learn what just shipped.

While the agent runs, the cockpit drafts a 2-minute briefing on the patterns it used — drawn from your diff, not a tutorial. Skim it, study it, or skip it. The next run lands wiser.

↳ lessons pulled from your code · the codebase remains yours
Instruments on the panel

Four instruments. Zero passengers.

We trimmed every feature that didn't earn its place on the panel. What's left is the loop: workflows, learning, locality, ontology.

Serious tools for serious builders
01WORKFLOWS

Agent workflows, not chat threads.

Save your best prompts as named workflows. Fork them, parameterize them, replay them. Your team's playbook becomes executable — and auditable.

↳ 4 saved · 142 runs · replays exportable
01 / INSTRUMENT
build-checkout
12× this mo.● ACTIVE
scaffold-feature
4× this mo.
audit-PR
8× this mo.
fix-bug-from-trace
2× this mo.
migrate-auth-flow
1× this mo.
02LEARNING

A companion that reads your diffs.

Every meaningful change becomes a 2-minute briefing on the pattern, the why, and what to watch for next. Pulled from your codebase. Quizzes optional.

↳ 12 briefings · 3 unread · graded by engagement
02 / INSTRUMENT
↳ PORT/ADAPTERread
Why your Stripe webhook lives in infra/
↳ GUARDSnew
Dependency direction, made cheap to enforce
↳ ASYNCqueued
When to put a queue between two adapters
03LOCAL-FIRST

Your repo. Your keys. Your disk.

Nothing leaves your machine without your say. Bring your own model keys (Anthropic, OpenAI, OpenRouter, Ollama). Trace, map, briefings — all on disk, all yours.

↳ 5 providers · BYO key · no vendor backend
03 / INSTRUMENT
~/.xexaflow/config.toml● local
● claude-sonnet-4.5anthropic
○ gpt-4.1openai
○ openrouter/autoopenrouter
○ ollama/qwen-2.5local
04ONTOLOGY

One model. Code, specs, agents, runtime.

Xexaflow indexes the whole stack into a single graph — your ports, adapters, intents, runs, learnings. Click a node, see what it touches. Nothing is hidden in a folder you forgot about.

↳ live graph · queryable · drift-aware
04 / INSTRUMENT
ONTOLOGYcodespecsagentsruntimelearningsintents
Crews on the runway

For builders who want leverage and literacy.

Xexaflow is not for everyone. It's for builders who'd rather understand their codebase than be afraid of it.

Learn as you operate
01
SOLO FOUNDER

The solo founder building two products in the air.

Limited engineering time, two products to keep alive. Needs the agent to ship reliably, and the codebase to stay reviewable when a co-founder or first hire shows up.

↳ a typical flight Replays last week's auth refactor before shipping the new one. Forks « build-checkout » into « add-magic-link ». The repo map shows the new adapter without redrawing the architecture. Investors ask: « who wrote this? » — they answer: « we did. »
“

I can fire a Loom of the agent trace at my advisor. They get it in two minutes.

— indie founder, $4k MRR
47
workflows saved
0
rewrites / quarter
02
VIBE CODER LEVELING UP

The vibe coder who finally wants the engine room.

Ships side-projects on weekends. Comfortable with prompts. Less comfortable explaining the architecture of anything they've ever shipped to anyone who asks.

↳ a typical flight Launches « build-checkout » Sunday night. The agent writes six files. Monday morning the briefing reads: why your Stripe webhook lives in infra/, not in your route handler. Ninety seconds. They get it now. Next time, they write the port themselves.
“

I stopped pasting code I don't understand into prod.

— self-described vibe coder
6×
more shipped
12
patterns / month
03
FREELANCE GOING SENIOR

The freelance who refuses to be deprecated.

Mid-career, technical, allergic to AI hype. Wants the leverage, not the lobotomy. Wants to be sharper in six months — not the same plus an autocomplete.

↳ a typical flight Sets a guard: « no port may import its adapter. » Runs the agent on a real feature. Reads the briefing on dependency direction, then writes their own version from memory. The codebase becomes a course taught by their own commits.
“

First AI tool that made me a better engineer, not a faster typist.

— 9-year backend dev
3.4×
lesson retention
100%
code understood
Pre-flight check

The questions we keep being asked.

Can't find what you're looking for? Email hello@xexaflow.dev — we read every one.

Question 01 / 04 answered

Is this for me if I'm a beginner?

If you can describe what you want to build in plain English and you're willing to read a two-minute explanation, yes. Xexaflow is built for builders mid-transition — comfortable with prompts, getting serious about their own codebase. We're not a tutor for absolute beginners, and we're not an IDE for senior staff engineers.

Where we're going

An operational ontology for the builder.

Unified

Today, your stack lives in fragments. Code in a repo. Specs in a Notion. Agents in a chat. Runtime in a dashboard. Knowledge in your head, until it isn't. The seams between them cost you hours, every week.

Xexaflow models the whole stack as one graph: code, specs, agents, runs, learnings — connected, queryable, navigable. You see what depends on what. You replay what just shipped. You ask the cockpit why your billing logic moved, and it tells you, with the diff and the briefing attached.

The endgame is simple: an operator who knows their stack at the depth a senior engineer knows hers — built up one workflow, one briefing, one replay at a time. Less hype, more leverage. Less magic, more mastery.

↳ signature
Serious tools for serious builders.
Read the manifesto
↳ Cleared for take-off

Stop flying blind in your own codebase.

247 founder-builders are on the runway. Drop your email — we onboard fifty at a time and we'll bring you in within two weeks.

↳ free during beta↳ no cloud upload↳ unsubscribe anytime