Toolport Studio
Your AI workspace. All of it.
For people who work across several AI coding providers and want one coherent desktop home
Start with a normal conversation and add a folder only when the work becomes a project. The same workspace brings in terminals, diffs, previews, source control, images, and governed Toolport tools without forcing every conversation into a repository-first flow.
01 / What it does
One workspace.
The providers you choose.
One window, every provider
Use Claude, Codex, Cursor, Grok, and OpenCode behind the same interface, with a curated model picker and the full catalog close at hand.
Bring your own access
Toolport Studio talks to provider CLIs already installed and signed in on your machine. It does not resell model access or turn API keys into subscription access.
Start without a project
Open a conversation with no repository attached. Add a folder, file, screenshot, or terminal when the task naturally grows into build work.
Real source control
Review diffs, changed files, branches, and commits in the same shell where the work happened instead of treating Git as an afterthought.
Terminals and previews
Bring up the local tools a task needs without leaving the conversation or adopting a different layout for each provider.
MCP tools through Toolport
When enabled, the local Toolport gateway gives every provider the same governed tool set while keeping tool-heavy coding turns lean by default.
02 / How it works
Begin with a thought.
Grow into the work.
- 01
Choose a provider
Use a provider CLI you already trust and pay for. Toolport Studio discovers the signed-in tools on your machine.
- 02
Start the conversation
Work without a folder or repository when that is all the task needs. Paste screenshots and switch models inside the conversation.
- 03
Add context deliberately
Attach a project, open a terminal, inspect a diff, launch a preview, or enable Toolport tools as the task becomes more concrete.
03 / Under the hood
Honest beta.
Real daily work.
Provider-neutral shell
Provider adapters sit behind one conversation model so the workspace can stay consistent while authentication and capabilities remain provider-owned.
Progressive context
A chat does not need to pretend it is a coding project. Project surfaces appear only after you attach the context that makes them useful.
Tested in real work
Claude, Codex, and Grok are heavily used and tested in real work. Cursor and OpenCode are lightly tested today, so those provider paths may still have more beta edges.
04 / Pricing
Clear terms.
No fog.
Free and open source under the MIT license. Use the provider subscriptions you already have.
Bring your providers into one desktop workspace.
Open Toolport Studio ↗