The local control plane for AI coding agents
Your context belongs to your project. Not to any harness.
Friday gives every agent you run one local brain — shared project memory, token-efficient context, deterministic plans and verified merges — while Claude Code, Codex and Cursor do the work on your machine.
The problem
Every harness keeps your context hostage.
Today each agent runs in its own terminal tab: a separate bubble that forgets yesterday, re-reads everything, and writes without asking. You cannot scale what you cannot trust.
Memory dies at the tool boundary
Sessions, indexes and notes live inside each tool. Switch hosts and the knowledge does not follow.
New host, blank slate
A fresh agent re-learns your architecture, conventions and history — at your expense.
Agents act while you look away
Files get overwritten and work duplicated while loops run unattended — nobody checks until it is merged.
Your code travels wholesale
Whole files ride along with every prompt to somewhere remote, whether they are needed or not.
Without Friday
Four tools, four private memories, zero shared truth.
With Friday
- Goals and plans
- Task history
- Memory and graph facts
- Policy and decisions
- Verification records
One memory beside your code. Every host reads from it; none owns it.
Meet Friday
One local brain. Every agent.
Friday is not another wrapper. It is real infrastructure, running strictly on loopback, that connects your agents into a single collaborative engineering team — with your codebase's memory anchored in an append-only local ledger.
- 01 Goal what you want
- 02 Plan how to get there
- 03 Tasks the unit of work
- 04 Agents any host runs it
- 05 Verify nothing ships unchecked
- 06 Git the code authority
The pillars
What no harness gives you.
Four things Friday does around your agents — memory, tokens, intent and verification — and the governance that wraps them.
Pillar 01 · Memory
Every agent shares one memory.
Yesterday's decisions, today's failures, the graph of your code: Friday anchors it all beside your repo in an append-only local ledger. Every agent reads from it; none owns it. Events are appended, never rewritten — replay reconstructs the whole state of the project.
Replay from #0001 rebuilds goals, plans, decisions and verification — without any tool's session history.
Pillar 02 · Tokens
Stop feeding the whole codebase into every prompt.
Traditional agent loops re-read entire files — thousands of tokens — on every turn. Friday's token-saving engine serves pre-computed AST slices instead: just the symbols a task needs, assembled locally from the code graph. Answers stay precise; bills stay small.
Assembled from the pre-computed code graph — a stat per file, nothing re-read, nothing sent wholesale.
Pillar 03 · Intent
Your intent survives every retry.
A deterministic DAG breaks each goal into dependency-aware tasks, each editing its own isolated Git worktree. When a model fails or a syntax retry loops, your boundaries hold: file reservations and task edges are preserved mathematically, not by convention.
Retries re-run the attempt — boundaries and reservations hold until the task ends.
Pillar 04 · Verification
AI can never lie to you.
Every finished task is treated as an unverified claim until automated linters, typechecks and test suites deterministically prove it passes. Only verified code merges into main — the model's word is never the gate.
A task completes when the checks pass — not when the model feels finished.
Governance
One click, without stealing your focus.
When an agent wants to write a file or run a command, the ambient Notch drops down from the top of your screen: allow once, for this run, or for the whole task. While something waits, the island never hides — and nothing proceeds without you.
Also on board
Everything else Friday runs for you.
The Studio
A spatial canvas of goals, tasks and agents — drawers to inspect anything, diffs before they land, and the duck keeping watch over every state change.
Routing and budget
The right model for every task, and it asks before anyone spends.
Recovery fencing
A wandering attempt is fenced back to its own worktree. A crashed run resumes — it never starts over.
Guided onboarding
Friday the duck walks you through the whole loop — four stops, two minutes, and you know everything.
Tray and shortcuts
Status, pause, halt and restart live in the tray; a global shortcut opens the Studio from anywhere.
One daemon per clone
Every project keeps its own private state on loopback — no cross-project bleed, no shared credentials.
The browser, too
The daemon serves the same Studio on loopback — open Friday's interface in any browser on your machine.
What we believe
Your context belongs to your project.
Not to a tool, not to a vendor. Friday's memory, events and graph facts live beside your code, in files and SQLite you can open and read.
You are always the decider.
Every write, every command and every dollar passes a human gate. Agents wait; you allow.
Done means verified.
Verification is not a suggestion. A task completes when the checks pass, not when the model feels finished.
Run your AI agents with Friday.
Stop babysitting terminal tabs. One installer, your machine, your repository.
Free while in development. Windows today.