Many agents. One braid.
Every agent framework wants you to live inside it. Braids is the layer that sits over them. Weave a CrewAI crew, a LangGraph workflow, your Claude Code MCP server, and a local Ollama backstop into one coherent pipeline. The agents don't have to know about each other — Braids does.
A canvas for stitching agents together.
Drop frameworks onto the canvas — CrewAI here, LangGraph there, an OpenAI Codex cell off to the side, Ollama at the bottom. Wire outputs to inputs. Set fallbacks. The full plan-code-test-push loop, made of pieces from whichever ecosystem does each part best. No more 'we standardized on framework X' — you can use them all.
Every run makes the next run better.
Every time a braid completes, Braids indexes the transcripts, the diffs, the test results, the failures. Future runs — across any framework — pull from that RAG. Your codebase teaches your agents what works in your codebase. After a month, no off-the-shelf agent setup matches what your braid has internalized about your stack.
Plan → Code → Test → Push. Unattended.
The opinionated default braid. Hand it a Linear issue or a feature spec. The architect agent plans it. The coder agent writes it. The tester agent runs it through SF Dynamo. The reviewer agent files the PR. You walk away. You come back to a passing pull request — or to a clear, readable explanation of why it stopped.
Your hardware. Your tokens. Your call.
Ollama is the default execution backend. The architect crew's planner runs on Llama. The coder runs on Qwen. The tester might call out to a hosted Claude for the tricky regression. Braids picks per task — based on what's available, what's free, and what you've configured. Your monthly inference bill goes from $10K to $0 — without giving up the smart calls when you need them.
Talks to Hopper, Threads, Dynamo, Focus.
Hopper is the launch surface. Threads is the engagement layer. Dynamo is the verifier. Focus is the message bus. Braids is what makes them feel like one product. When SF Threads finishes a plan, it hands the build to Braids. When Braids finishes a feature, it hands the test to Dynamo. When Dynamo greenlights, Hopper pings you. The suite isn't a marketing word — it's how the work moves.
SF Braids works with the rest.
The reason Speedforge isn't just five tools sitting next to each other.
SF Hopper
Hopper is the launchpad — Braids sprints run inside the workspaces it manages.
SF Dynamo
Braids hands the finished feature to Dynamo for real-device verification.
SF Threads
Threads is the input — every plan it drafts is a candidate for a Braids sprint.
SF Focus
Focus keeps Braids running on the right machine and routes its events.
Theme song · TBD — pitch one to Sarah