Coming soon on Windows
Give Bwat a folder and let it work
The same agent engine, built for long-running work on your PC
The Windows app brings Bwat's local agent to people who do not live in an editor or terminal. Choose a folder, describe the outcome, and let the run continue while you move around the app or step away from the screen.
Windows is the first desktop release. Availability is controlled while the app is prepared for release.
This is Bwat for work on this computer
- Choose the exact folder the agent may work in
- Read, edit, create, and organise local files
- Run commands and use approved local tools
- Leave an active run and return to its live session
A local workspace, not a second cloud drive
Your chosen folder remains the source of truth. The local runtime reads and changes files on the computer, and the conversation for that work is stored locally. When the model needs to reason, the relevant context is sent through Bwat's service, just as it is in VS Code and the CLI.
- The folder picker defines the agent's working boundary
- Files are changed in place instead of uploaded into a new file system
- Local conversations are clearly separated from cloud chat history
- Closing the app or signing out ends active local runtimes
Work that suits the desktop app
- Sort and summarise a directory of reports
- Turn scattered notes into a finished document
- Apply the same change across a large group of files
- Drive a supported local application such as Blender
Designed for work that takes a while
Runs outlive the screen
Navigate away from an active Work conversation and return without restarting the task.
One clear boundary
Bwat starts from the folder you chose, so both you and the agent know what is in scope.
Several jobs at once
The desktop session manager can keep up to four active local runs, each with its own folder and conversation.
Local application tools
The local runtime can connect to supported applications on the same computer. Blender is the first built-in integration.
Manual or Full Auto
Choose whether actions pause for approval or proceed automatically inside the granted workspace.
The shared Bwat engine
Windows, VS Code, and the CLI use the same agent core rather than three separate assistants.
What the preview means
- Is the Windows app available now?
- It is not generally available yet. Windows is the first desktop target, and access stays controlled while packaging and release work are completed.
- Does everything stay on my computer?
- Files and local conversation records stay on the computer. Relevant content still has to be sent through Bwat's service to the configured inference provider for the model to reason about it.
- Why not use VS Code?
- Use VS Code for software work and native diff review. The Windows app is for any folder-based task and for local applications, without requiring an editor or terminal.
Have a long-running local workflow in mind?
Tell us what is in the folder, what the finished result should be, and which application Bwat would need to work with.