WITHOUT — the alt-tab loop
- Terminal app
cd … again - Editor
find the file again - Git client
locate the diff again - AI chat in a browser
paste the context again - SSH session
re-orient again
v0.9.13 · open source · no account requiredThe whole project.
The whole project.
One window.
Terminal, files, editor, Git review, AI agents, containers, and remote rigs — all pointed at the same working directory. Stop re-explaining your project to five different apps.
$ why termco
Your context is the most expensive thing you rebuild every day.
WITH — one workspace
- Terminal · files · editor
same directory - Git review
beside the change - AI agents
already have context - Preview + containers
one glance away - Remote rigs over SSH
same workspace model
- No account, everInstall, open a folder, work.
- Your AI providerHosted, compatible, or fully local.
- Open sourceApache-2.0, end to end.
- Forkable pluginsReplace any part you disagree with.
$ termco --tour
Watch it work.
Every capture below is the real application. No mockups.
01 / agents
AI that shows its work.
Chat, launch managed coding agents, or connect an MCP client — against the workspace you're looking at. Every tool call and file change stays visible, gated behind your approval.
your keys · your provider · even local models
02 / git
Review diffs where you made them.
Git review lives beside the working tree. Checking an agent's change — or your own — means glancing sideways, not finding your place in another app.
03 / preview
See the app beside its code.
Run a local service and open its Preview next to the editor. Change, glance, repeat — the loop never leaves the window.
04 / remote
Local feel. Remote reach.
Connect an SSH rig, browse its files and containers, forward ports, hand the same directory to an agent. Only the machine changes.
05 / plugins
Fork the parts you disagree with.
The whole runtime is plugins that release independently. Don't like how a piece works? Fork it, edit it, replace it — restore the original any time.
fork → edit → verify → replace- WorkflowsRepeatable project tasks
- MCP clientsExternal clients, same context
- Port forwardingRemote services, local feel
- ContainersManaged beside their code
- Protected secretsOS-protected, on-device
- LSP + searchEditor feedback, fast search
- Team profilesOrg security controls
- Independent updatesUpdate only what changed
$ termco --install
Try it on a real project.
Releases live on GitHub. Download, open a folder you actually work in, and see if the window feels smaller than five apps did.
Separate builds for both chips from the latest GitHub release.
Download for macOSWSL projects work through the same workspace model.
Download for WindowsPick the package format for your distribution.
Download for Linuxapp: termco-ai/termco · plugins: termco-plugin-releases
$ man termco
Questions, answered.
Anything else — open a discussion on GitHub. The whole project is public.
Is Termco free?
Yes. Open source under Apache-2.0 — the application, the plugin contracts, and the release process are all public.
Do I need an account?
No. Install Termco and open a workspace — nothing is gated behind a login.
Which AI providers work?
Whatever fits the project — hosted providers, compatible endpoints, or local models. External MCP clients can connect to the workspace too.
Where do my credentials live?
On your device, behind OS-protected storage. They don't need to pass through Termco services.
How do updates work?
The app and its plugins release independently. Update only what changed — and roll a plugin back any time.