Local-first by design
Your model, index, history, and source code remain on your machine.
Local-first AI for developers
Most chat agents struggle with Ollama and small models. OwA is built specifically for developers running practical local hardware—with focused tools that help 4–9B models work clearly inside a real repository.
Your LLM runs on your machine. Your code stays on your machine. OwA works within your workspace—nothing leaves your hardware.

$ owa index .
scanning workspace…
✓ 1,284 files indexed locally
$ ask "where is auth handled?"_
Why OwA exists
Most coding agents assume a giant cloud model. OwA starts with the hardware developers already own, then makes focused local models genuinely useful.
Your model, index, history, and source code remain on your machine.
Clear tools and compact context help 4–9B models do focused, useful work.
Workspace boundaries and explicit confirmations keep actions inspectable.
Inside the workspace
Focused tools for the work developers actually do, connected to the model running on their machine.
Index the project locally and find the files that matter by meaning, not filename.
› owa index ./workspaceRead, edit, and patch targeted locations while keeping every change reviewable.
› owa patch --confirmInspect status, diffs, and recent history without leaving your repository.
› owa ask "what changed?"Run structured Python checks and confirm shell actions before they execute.
› owa review app/Under the hood
A lightweight Python app, direct Ollama integration, local indexing, and a compact tool system you can understand.

Keep OwA building
If OwA helps your local workflow, sponsorship keeps the project maintained, documented, and improving.