← Back to AtashiAtashi Desktop
Work Mode, without the terminal.
A desktop app for Windows, macOS and Linux that runs your Atashi team on your own machine — so the work happens where your files already are, and the engine just works.
Download · version 1.0.3
All three builds come from the same code, cut at the same moment. Every build hosts the full app and ships the local Work Mode engine inside.
Windows will show a “Windows protected your PC” warning — this build is not yet code-signed. Choose More info → Run anyway only if you downloaded it from this page.
SHA-256 checksum
2cadff3e2f43c5f4bcb7181e9939a29bbf305dbcfe5058bcb0d96db81a3c6f691. Unzip, then move Atashi.app into your Applications folder before you open it — don’t run it from Downloads. This step is not tidiness: launched from Downloads, macOS runs it from a hidden, read-only copy elsewhere on disk (Apple calls this App Translocation), and it can sit there for several minutes with no window, no dock icon and no error while it fails to start. Moving it first avoids that entirely.
2. In Terminal, once it's in Applications: xattr -cr /Applications/Atashi.app — this build has no code signature yet, so without this step Gatekeeper's first response is usually “Atashi is damaged and can’t be opened” (a stock unsigned-app report, not real corruption; right-click → Open alone will not clear it). Still blocked after that? System Settings → Privacy & Security, scroll to the blocked-app notice, click Open Anyway.
3. Double-click to launch. On an Apple Silicon Mac (M1 and later), use this same build — macOS runs it through Rosetta 2 and offers to install Rosetta the first time if it isn’t there. A native Apple Silicon build follows once the app is code-signed.
SHA-256 checksum
6cc9b7d3719fbd9c56193326d677b9010df58c2bd6170eb3ce8fe5677e043018Make it executable first: chmod +x Atashi-1.0.3-x86_64.AppImage — and if FUSE complains, run it with --appimage-extract-and-run.
SHA-256 checksum
3b8c1bb12ed84993be46ea0fef3ff9b5db62f20636409df55751ab089322508cRead before you install — the honest print
- The Windows and macOS builds are unsigned. The warnings above are your operating system doing its job; we say so here instead of teaching you to click through them blindly. Code-signing is in progress. Until then, the checksums beside each download are your integrity check — verify with
sha256sum(orshasum -a 256on macOS). - There is no auto-install, but the app now tells you. From 1.0.0 onward Atashi checks for a newer published version and says so inside the app; it never downloads or installs anything by itself. When it tells you, you come back to this page. Deliberate: an update channel that could install code without code-signing would be a door into your machine.
- Only the Linux build has been run by human hands so far. Windows and macOS are built from the same code and verified from inside the packages, but have not yet been hand-tested on real hardware. If you hit something on those, please tell us.
What it does
The desktop app hosts the full Atashi experience — your office, your team, Talk and Work Mode — in one window. The difference is what runs underneath: it supervises the local engine for you as a managed background process, so Work Mode is live the moment you open the app. No terminal to keep open, no setup to remember.
On the web, Work Mode needs that engine running on your computer; if it isn't, the office simply can't reach your files. The desktop app removes that step entirely — it starts the engine, watches it, and restarts it if it stops.
Why it runs on your machine
Work Mode acts on your files and tools, so by design the cloud never reaches into your computer — your machine talks to a local engine, and that engine never accepts a connection from the outside. The desktop app hosts that engine for you, which is how you get real Work Mode without babysitting a terminal window.
Built secure
Your sign-in is stored in your operating system's own credential store — Windows Credential Manager, macOS Keychain, or your Linux keyring — not a browser cookie. Your team's skills and safety checks stay server-side — the app ships none of that logic — and every action still passes the same server-side approval and safety scan as the web app. Nothing runs on your files without your explicit go.