3x-haust/ondra

English · 한국어
Ondra is an agent workspace for macOS. Tell the main chat what you want, once. It splits the work into jobs, each job sees its part through to the end on its own branch, and the result comes back to main: what changed, why, and how it was checked. Long, hard-to-read model output turns into progress, changed files, screens and choices.
One chat, many jobs
Main plans, hands out the work and reports back. You don't have to watch each job.
Work and personal, kept apart
Each space has its own git accounts, browser logins, memory, devices and history.
Shown, not told
Plans, to-dos, diffs, before/after screenshots, test results and diagrams instead of paragraphs.
Proof, not claims
Every "done" is checked against what the job actually ran. Whatever wasn't checked says so.
## How it works
Main splits the work. "Build me a portfolio site" becomes checking the material, finding references, planning, building and verifying, and each step starts when the one before it is done. Every project folder gets its own chat, and jobs started there work in that folder.
Each job has a fresh start. A job works in its own git worktree, starting from the latest remote code, so jobs never overwrite each other or the folder you are working in. More work on a finished job starts a new job that takes over its branch and results. When you change direction mid-way, the old job wraps up and a new one picks up.
Results come back to main. When a job ends, main tells you in its own words, shaped to the work: the cause, the fix and the check for a bug; what changed for a feature; what went out for a release; the answer and its sources for research.
It only asks what needs you. Questions that need your intent or taste come up with choices and the context behind them. Pick one and press Enter, or write your own answer. You can also step into any running job and redirect it.
## Spaces
Work and personal are separate workspaces, not filters. Switching spaces switches everything:
Accounts: commits, pushes, PRs and terminals run as that space's git identity and GitHub login. A space without one says so instead of borrowing the other's.
Browser: logins and cookies stay in their space.
Memory and skills: what Ondra learned in one space is used only there.
Devices: each simulator and emulator belongs to work, personal or both.
History: search, side chat, btw and the input history see only this space. Jobs can't read other jobs' or other spaces' files and logs.
## What jobs can see and use
Shared browser. A real Chrome inside the app, with a tab per job. Sign in once in the panel and that space's jobs use the session. Passwords come from the macOS Keychain and never reach the model. With Aside installed, jobs browse through it.
Computer use. Native Mac app automation requires a separately prepared, isolated macOS guest. It does not control windows already open on your Mac. Known host desktop commands are blocked, including process-targeted input; without a verified guest connection, native app automation stops instead of switching to your desktop. These command checks are not an OS sandbox for arbitrary shell commands.
Device use. Each job makes its own iOS simulator or Android emulator, leaves screenshots as evidence and removes it when done. You can watch and touch the screen from the device panel. Emulators render on the Mac GPU and idle when nothing changes.