# Digital Freedom

> Frontier is a locally-run, browser-based agentic coding tool for orchestrating multi-repository AI-assisted development.

## Product

- [Home](https://digitalfreedom.app/): Overview of Frontier, the local agentic coding orchestrator.
- [Plans & Pricing](https://digitalfreedom.app/plans): Free, Pro, and Enterprise plans.
- [Download](https://digitalfreedom.app/download): Get Frontier for macOS, Windows, or Linux.
- [Release Notes](https://digitalfreedom.app/release-notes): What shipped in each version, most recently v1.10.1.

## Documentation

- [Help Center](https://digitalfreedom.app/help): FAQ and full guide index.
- [What is Frontier?](https://digitalfreedom.app/help/getting-started): The short version: one place for your ideas, repos, and agents to live together.
- [Picking your context](https://digitalfreedom.app/help/picking-your-context): First launch asks who you are, not for a password — here's why, and what the setup walks you through.
- [Your first week with Frontier](https://digitalfreedom.app/help/your-first-week): A rough on-ramp: what to try on day one, and what to reach for once the basics feel automatic.
- [Settings that apply everywhere](https://digitalfreedom.app/help/settings-and-defaults): The handful of baseline choices every workspace inherits — where work lands, and which coding CLI runs it.
- [Customizing the prompts behind every run](https://digitalfreedom.app/help/customizing-your-prompts): The instructions Frontier wraps around your messages are editable — and worth reading once before you change them.
- [Workspaces & Threads](https://digitalfreedom.app/help/workspaces-and-threads): Your project's home base — repos, conversations, and history, all attached to one place.
- [Diffs, history, and editing files directly](https://digitalfreedom.app/help/diffs-history-and-files): Every change a conversation makes stays visible — as an inline diff, a running history, or a file you can open yourself.
- [Organizing bigger projects with phases](https://digitalfreedom.app/help/organizing-bigger-projects): A big initiative doesn't have to live in one workspace — nest smaller ones underneath it instead.
- [One-off conversations](https://digitalfreedom.app/help/one-off-conversations): Sometimes you just want to ask something — a floating panel skips creating a workspace entirely.
- [Revision history](https://digitalfreedom.app/help/revision-history): Every edit to a workspace, domain, or agent is recorded automatically — what changed, from what, to what.
- [Domains](https://digitalfreedom.app/help/domains): Write down what your codebase needs an agent to know, once, and stop repeating yourself.
- [Keeping Domains and repositories in sync](https://digitalfreedom.app/help/domains-and-repositories): A Domain's notes only help if its workspace can actually see the code they describe.
- [Writing a Domain that actually gets used](https://digitalfreedom.app/help/writing-a-domain-that-gets-used): The difference between a Domain that helps and one nobody reads comes down to a few habits.
- [Agents & the Conductor](https://digitalfreedom.app/help/agents-and-conductor): Two different kinds of automation — a one-off nudge, and something that keeps going on its own.
- [Tuning how often an agent checks in](https://digitalfreedom.app/help/tuning-agent-cadence): How often an agent looks, and how long it's allowed to run, are both yours to adjust.
- [Reading the Audit Trail](https://digitalfreedom.app/help/reading-the-audit-trail): When an agent didn't do what you expected, this is the first place to look — not the last.
- [Reusable Strategies](https://digitalfreedom.app/help/strategies): Save a multi-agent pattern that worked, and bring it to life again with one click.
- [Root roles vs. their own workspace](https://digitalfreedom.app/help/root-roles-vs-their-own-workspace): The one real judgment call when designing a role: does it need a space of its own?
- [Referencing sibling roles in a prompt](https://digitalfreedom.app/help/referencing-sibling-roles): One role's instructions can point at another by name — resolved automatically the moment you instantiate.
- [Forking the built-in Watcher/Addresser and Engineer/Reviewer strategies](https://digitalfreedom.app/help/forking-the-built-in-strategies): Two proven patterns ship ready to copy — start there before designing one from scratch.
- [A notebook your agents share](https://digitalfreedom.app/help/memories): Small, lasting notes — what worked, what broke, what's worth remembering next time — attached to whatever they're about.
- [Turning a highlight into a memory](https://digitalfreedom.app/help/turning-a-highlight-into-a-memory): You don't have to wait for an agent to notice something — select the text yourself.
- [Connectors](https://digitalfreedom.app/help/connectors): Frontier speaks Claude Code and Codex natively — and leaves the door open for other coding agents too.
- [Choosing a connector per workspace](https://digitalfreedom.app/help/choosing-a-connector-per-workspace): Most people never touch this — it's there for the rare project that wants something different.
- [What "scaffolded" means for the newer connectors](https://digitalfreedom.app/help/what-scaffolded-means): A couple of connectors exist as an early sketch, not a tested guarantee — worth knowing before relying on one.
- [MCP Server](https://digitalfreedom.app/help/mcp-server): For advanced setups: let another agent drive your entire Frontier install directly.
- [What an agent can do through the MCP server](https://digitalfreedom.app/help/what-an-agent-can-do-through-mcp): Nearly everything you can click through in the app has an equivalent an outside agent can call directly.
- [Global Search & the Account Menu](https://digitalfreedom.app/help/search-and-navigation): Find anything — a workspace, a Domain, a file — from anywhere, without touching the mouse.
- [Keeping a growing workspace list tidy](https://digitalfreedom.app/help/keeping-your-workspace-list-tidy): A handful of small touches for once you've got more workspaces than fit on one screen comfortably.
- [Admin & User Profiles](https://digitalfreedom.app/help/admin-and-identity): For installs shared by more than one person — who's who, and who can manage what.
- [Sharing one install with your team](https://digitalfreedom.app/help/sharing-one-install-with-your-team): One Frontier install, running on one machine, can genuinely serve more than one person.
- [Moving a workspace between contexts](https://digitalfreedom.app/help/moving-a-workspace-between-contexts): Handing off one project to someone else's space, without dragging your whole setup along with it.
- [Backing up and restoring your setup](https://digitalfreedom.app/help/backing-up-and-restoring-your-setup): Your entire setup — every workspace, every conversation, every setting — can travel with you to a new machine.
- [Create your first workspace](https://digitalfreedom.app/help/tutorial-first-workspace): The smallest complete loop — a repo, a workspace, and one real conversation.
- [Build a Watcher / Addresser strategy](https://digitalfreedom.app/help/tutorial-build-a-strategy): Wire up two agents that hand work to each other — from a blank page to a running pipeline.
- [Set up an Engineer / Reviewer pipeline](https://digitalfreedom.app/help/tutorial-engineer-reviewer-pipeline): A second set of eyes on everything you build — wired up once, running from then on.
- [Recover from a stuck agent](https://digitalfreedom.app/help/tutorial-recover-a-stuck-agent): A quick checklist for the moment an agent seems to have gone quiet and you're not sure why.

## Blog

- [Release v1.8.0: Two instruments, one studio](https://digitalfreedom.app/blog/v1-8-0-two-instruments-one-studio): Codex CLI now runs inside Frontier the same way Claude Code does, and wiring up either one is a single step you can redo whenever you like. Same workspaces, same agents, same memory. Your choice of instrument.
- [Release v1.7.1: A quieter kind of motion](https://digitalfreedom.app/blog/v1-7-1-a-quieter-kind-of-motion): The website's scroll animations get simpler, section labels get a small flicker of static as they arrive, and the wordmark loses a little weight. Nothing new to learn — everything just moves better.
- [Release v1.7.0: Thirteen real places to start](https://digitalfreedom.app/blog/v1-7-0-thirteen-real-places-to-start): Every example on the site now applies against a service you already have an account with. Two fixes in flight never collide anymore. And the wordmark has a small new mark.
- [Release v1.6.1: The handshake that never happened](https://digitalfreedom.app/blog/v1-6-1-the-handshake-that-never-happened): A small release with two changes: the bridge between Frontier and your terminal was missing a piece in the v1.6.0 installers, and trying an example from the website now asks where you want it.
- [Release v1.6.0: Meet Frontier](https://digitalfreedom.app/blog/v1-6-0-meet-frontier): A new name for the same idea, a link you can click from the website that builds a working setup inside the app, and four examples to start from.
- [Release v1.5.0: Bring your work with you](https://digitalfreedom.app/blog/v1-5-0-bring-your-work-with-you): Pull any repository off GitHub without touching a terminal, find your way around a screen you have never opened before, and start the thing an empty list is asking you to start.
- [Release v1.4.0: One timeline for everything that happened](https://digitalfreedom.app/blog/v1-4-0-one-timeline-for-everything-that-happened): A single feed of every conversation, change, and memory across your entire setup, a revision history that remembers what a workspace used to be, and macros you can drop into a message just by typing a curly brace.
- [Release v1.3.0: The parts you never see, working harder](https://digitalfreedom.app/blog/v1-3-0-the-parts-you-never-see-working-harder): A new foundation under every workspace and thread, replay you can actually read, and a handful of rough edges sanded down.
- [Introducing Frontier](https://digitalfreedom.app/blog/introducing-frontier): Why I built a place for your ideas to keep moving, instead of one more chat window that forgets everything overnight.
- [The Conductor pattern: one agent that never writes code](https://digitalfreedom.app/blog/the-conductor-pattern): How one agent keeps an entire roadmap moving forward — without ever opening a single file.
- [Domains: giving every agent a memory it can trust](https://digitalfreedom.app/blog/domains-and-context): A place for what your codebase has already taught you, so no agent has to learn it twice.
- [Five ideas, one afternoon](https://digitalfreedom.app/blog/five-ideas-one-afternoon): Why exploring a fork in a decision is cheaper than arguing about it — just build both and see.
- [A co-founder for your side project](https://digitalfreedom.app/blog/a-co-founder-for-your-side-project): Solo builders rarely have someone to push back on their own work. An Engineer/Reviewer pair fills that gap.
- [Watch the feedback, so you don't have to](https://digitalfreedom.app/blog/watch-the-feedback-so-you-dont-have-to): A Watcher/Addresser pair turns pull request comments into fixes before you've finished your coffee.
- [The assistant that remembers your research](https://digitalfreedom.app/blog/the-assistant-that-remembers-your-research): Long research threads lose their best insights to scroll-back. Give the good parts a permanent home.
- [Release v1.0.0: A front door, and everything real behind it](https://digitalfreedom.app/blog/v1-0-0-a-front-door-and-everything-real-behind-it): Frontier's first tagged release: a public home on the web, an identity that syncs across machines, and real logins, downloads, and email delivery in place of every placeholder that came before.
- [Why "save time" is the wrong way to think about AI](https://digitalfreedom.app/blog/why-save-time-is-the-wrong-way-to-think-about-ai): Every generation gets tools that make the old work faster — the real question is what work becomes possible that wasn't before.
- [How to stop starting every morning triaging the same GitHub issues](https://digitalfreedom.app/blog/automate-issue-triage-with-a-scheduled-agent): A scheduled agent can check your repo for new issues on its own, then hand each one through a triage-reproduce-fix pipeline of its own threads — so the chore that used to eat the first twenty minutes of your day happens before you've opened your laptop.
- [How to save a multi-agent setup so you're not rebuilding it every time](https://digitalfreedom.app/blog/strategies-reusable-agent-patterns): A Strategy captures a set of agent roles once — triggers, prompts, and workspace scope included — so a pattern like Watcher/Addresser or Engineer/Reviewer can be instantiated again with one call instead of rebuilt by hand.
- [What comes after the IDE?](https://digitalfreedom.app/blog/what-comes-after-the-ide): An IDE was built around one assumption — one person, at one keyboard, working on one file at a time — and that assumption, not the editor itself, is the first thing worth questioning.
- [How to know what happened across every project overnight — without opening any of them](https://digitalfreedom.app/blog/a-morning-briefing-for-every-project-you-run): A scheduled agent can quietly check every workspace you're running and leave one digest waiting for you, so catching up stops meaning opening ten different projects one at a time.
- [Can you use more than one AI CLI in the same project?](https://digitalfreedom.app/blog/mix-ai-clis-one-project): Frontier never hard-codes which AI CLI an agent runs — pick one as the install-wide default, then override it per workspace, so one project's Reviewer can run on a different tool than its Engineer without rebuilding anything.
- [Release v1.1.0: A sturdier lock, and a few loose ends tied up](https://digitalfreedom.app/blog/v1-1-0-a-sturdier-lock-and-a-few-loose-ends-tied-up): This release closes a real local-tampering gap in your plan and usage limits, fixes two DocViewer regressions, brings a shared visual flourish to the client app, and folds the Status Report hub's scratch workspace into something more permanent.
- [Why good ideas get shelved before anyone decides they're bad](https://digitalfreedom.app/blog/why-good-ideas-get-shelved): Most ideas aren't rejected for being bad — they're rejected on a cost estimate, and the real measure of a new tool is how many of those estimates it quietly proves wrong.
- [Loop engineering: the real skill isn't the prompt, it's the loop](https://digitalfreedom.app/blog/loop-engineering): A single great prompt gets you one good answer. A well-designed loop — with its own trigger, interval, and exit condition — gets you a process that keeps working after you've stopped watching.
- [Release v1.1.5: A smoother handshake, and a subscription that finally adds up](https://digitalfreedom.app/blog/v1-1-5-a-smoother-handshake-and-a-subscription-that-finally-adds-up): This release makes sure a brand-new context actually gets Claude Code wired up from the start, fixes extra contexts showing the wrong plan, and adds a quiet nudge when a new version is ready.
- [Release v1.2.0: Replay any message, and a few blind spots closed](https://digitalfreedom.app/blog/v1-2-0-replay-any-message-and-a-few-blind-spots-closed): This release lets you replay a single message's tool calls instead of a whole thread, fixes a workspace with more than one repo only exposing the first one, and makes scheduled runs recover instead of silently dropping a message.
- [Build a product team that didn't exist yesterday](https://digitalfreedom.app/blog/build-a-product-team-that-didnt-exist-yesterday): Nobody hands you a Product Lead or a roster of Feature Engineers pre-cast. Imagine who you'd actually want running point, then write them into being.
- [How to work on 10 things at once (or more)](https://digitalfreedom.app/blog/work-on-ten-things-at-once): A roadmap workspace and one Conductor agent can carry ten separate improvements through their own build-review-merge cycle, one after another, so the only thing left for you to do is add the next item to the list.

## Company

- [About](https://digitalfreedom.app/about): Why we built Frontier.
- [Contact](https://digitalfreedom.app/contact): Get in touch.