01
Windows, first class.
A native Windows 10/11 direction. Real PowerShell, CMD, and Git Bash sessions through ConPTY. No WSL detour.
Product direction TERMINALONE / BUILT FOR WINDOWS
One terminal.
Every shell.
Your favorite shells. One thoughtful workspace. Built for developers who make Windows their own.
01 / THE WORKSPACEDESIGN CONCEPT
YOUR TOOLS. YOUR FLOW.
PowerShell
A familiar shell. A fresh perspective.
A workspace designed around your Windows workflow.YOUR TOOLS. YOUR FLOW.
CMD
The classics deserve a better home.
Keep the tools you know. Make room for what comes next.YOUR TOOLS. YOUR FLOW.
Git Bash
Your everyday tools. All together.
Bring your Git workflow into a space that feels like yours.TerminalOneMADE TO FEEL LIKE YOURS
Same place to build.
PowerShell
Command Prompt
Git Bash
Planned native support THE VISIONLess friction.
Less friction.
More flow.
Great tools get out of your way.
We’re building a terminal that feels
like it belongs in your workflow.
02
Space to find your flow.
An iTerm2-inspired experience with thoughtful tabs, split panes, and typography. Built to put your work in focus.
Product direction03
Your machine. Your control.
A local-first foundation. No mandatory account, no remote backend, and no telemetry in the initial application scope.
Product direction THE NEXT CHAPTERA smarter shell.
A smarter shell.
A careful approach.
The terminal should adapt to the developer, not the developer to the shell.
That’s the idea behind our future intelligent shell adapter. Understand supported command intent, respect the environment, and choose a safe path forward.
Explore the adapter roadmap Planned capability
Your command. Your intent.Understand. Then resolve.Shell awareness · explicit fallbacks
PowerShellCMDGit Bash
No arbitrary script rewriting. No silent state switching.
BUILT WITH INTENTIONGood foundations.
Good foundations.
Then, what’s next.
A focused roadmap, one reviewable step at a time. Follow the work from the first foundation to a future public beta.
See the full roadmap- 01Phase 0
The foundation
Architecture, security, tooling, and CI.
- 02Phase 1
A real native terminal
ConPTY sessions, shell discovery, and lifecycle.
- 03Phase 2
A place for your workflow
Terminal tabs, splits, themes, and navigation.
- 04Phase 3
Intelligence, thoughtfully
Conservative recognition and safe shell strategies.
A FEW ANSWERSBefore the
Before the
first command.
Can I download TerminalOne today?
Not yet. TerminalOne is in development.
There is no published installer at this stage. Follow the GitHub roadmap for implementation progress and future release information.
Will I need WSL or a cloud account?
Neither is part of the core application requirements.
The goal is a Windows-native application that runs your installed shells locally. A developer toolchain may be needed to build the desktop app from source.
Does it automatically translate Bash into PowerShell?
No. The intelligent shell adapter is a planned capability.
The approach is conservative: recognize supported intent at safe command boundaries, respect shell state, and offer explicit fallbacks. Arbitrary scripts will not be automatically rewritten.
Is TerminalOne open source?
TerminalOne uses the MIT license.
The repository is currently private while the foundation is being established. GitHub links require repository access until the owner makes the project public.
Make room for
what’s next.
Follow the build. Explore the ideas.
Help shape the terminal you want to use.
MIT licensed Windows-native direction In development