A quiet workspace for ambitious ideas
Website & downloads · Releases · English · 简体中文
asHub is an open-source desktop workspace powered by agent-sh. Keep conversations, models, subagents, terminals and project files together, with a readable result and an inspectable execution trail.
Available for macOS (Apple Silicon / Intel), Windows x64 and Linux x64. The desktop app and local browser view share the same client. Connect your own model provider with API credentials or supported Codex sign-in; provider billing and plan limits apply.
Current interface with isolated demo data. English main screenshot; no personal conversations or credentials.
New in v0.21.5: a dedicated personal assistant conversation with scoped long-term memory, opt-in project continuation, browser file and code-editor workflows, and refreshed Codex models after switching accounts.
| Capability | Experience |
|---|---|
| Sessions & projects | Create and delete conversations within projects; sort sessions by recent activity, search, pin, archive and restore history |
| Conversation collaboration | Send tasks, follow receipts, supplement work and surface blockers to the coordinator; optional Git worktrees isolate changes |
| Readable execution | Replies and progress first; thinking and tool output stay in expandable details |
| Tasks & subagents | Task progress and five specialists: plan, explore, review, research and implement; configurable models and budgets |
| Models & context | Codex sign-in, model search and native thinking levels; inspect context and reported cache usage |
| Reviewable actions | Permission prompts, change previews, session-wide approval and background notifications |
| Project tools | PTY terminals, file browsing, image input, inline image previews and a skills marketplace |
| Plugins | Enable included extensions or import trusted ZIPs; configure, disable, uninstall and restore |
| Background mode | Keep tasks and remote access running when windows close; reopen or quit from the tray |
| Proxy controls | Choose a global proxy default and override it per conversation |
| Persistent work | Saved conversations, branches, rewind, Markdown export and downloadable workspace results |
| A consistent interface | Warm light and graphite dark themes; English and Chinese; display scaling and a collapsible status bar |
| Mobile access · preview | Continue authorized desktop conversations from a phone; shared history, streaming replies and one-time approvals |
Dark workspace
Project files
Download from the website or GitHub Releases. Desktop packages include their runtime; no separate Node.js installation is needed.
| Platform | Package |
|---|---|
| macOS Apple Silicon | arm64.dmg |
| macOS Intel | x64.dmg |
| Windows x64 | Setup.exe |
| Linux x64 | .AppImage |
- Install and open asHub
- Configure your provider and default model in the right panel, or use supported Codex sign-in
- Create a session, choose a project directory and start a conversation; open files, terminals and other panels as needed
curl -fsSL https://raw.githubusercontent.com/firslov/asHub/main/install.sh | bashThe script detects Apple Silicon or Intel, installs to /Applications and removes the quarantine flag. If a manually installed DMG is blocked, choose Open Anyway in System Settings → Privacy & Security, or run:
/usr/bin/xattr -dr com.apple.quarantine "/Applications/asHub.app"Install Git for Windows to use Bash commands and Git worktrees. asHub detects standard and per-user Git installations automatically.
After downloading the AppImage, run these commands in its directory:
chmod +x ./asHub-*.AppImage
./asHub-*.AppImageContinue desktop conversations at asHub Mobile. Requires asHub v0.20.5 or later.
- In the updated desktop, enable Device interconnect (设备互联) under Plugins → Local extensions, open its toolbar entry, and choose Allow access to this computer. Sign in or register and confirm shared directories. Earlier versions use Mobile Access; upgrading preserves existing device identity and authorization.
- Save the recovery code, then select I have saved it (我已保存). Unconfirmed codes survive menu switches, but must be saved before quitting or refreshing the app
- Sign in with the same account on your phone, select your computer, and continue a conversation or start a new one
Keep the computer online, awake and asHub running. In v0.20.8, enable Settings → Background activity → Keep running when the window closes to keep remote access available after closing the window. Background mode is off by default; quitting the app stops it. Optional sleep prevention allows the display to turn off, but does not guarantee access during lid-close or manual sleep.
Only conversations in authorized, existing directories are shared; restore archived conversations on the desktop first. Mobile supports streamed replies, images, model switching and one-time approvals. The relay forwards content without persisting conversation bodies; it is not end-to-end encrypted.
Project views, task receipts, result downloads and thinking controls require desktop v0.20.6 or later and an updated mobile gateway.
Open Plugins in the right toolbar to import a trusted plugin ZIP, review its setup and manage configuration. Optional features use the same menus and design as the app. Some kernel extensions take effect when a conversation next starts.
In v0.21.3+, open Plugins → Local extensions to enable Kimi Coding Plan, Project management or the Conversation browser. Uninstalling an included extension keeps it removed across updates; use its reinstall button to bring it back disabled without a ZIP. These extensions ship with asHub and start disabled. Existing manual installations keep their settings and take precedence. Start a new conversation to load enabled tools. Use /kimi-login for Kimi web sign-in.
In v0.21.4+, Image Display is also included as an optional local extension. Enable it to show workspace charts and screenshots inline, with click-to-enlarge previews. Images remain scoped to their conversation and are available through authorized mobile access. Project Management also gains task-bound blocker notifications with deduplication and delivery receipts; routine updates remain in the normal task flow.
The Conversation Browser opens a page beside the conversation, with isolated per-conversation site logins and manual takeover. In v0.21.5, it supports long text and supported code editors, workspace file uploads and reviewed downloads. Operations require approval by default; automatic approval is a per-plugin option. Download file confirmation and persistent browser grants remain desktop-only. Browser automation requires Electron.
The separately installed Personal Assistant plugin requires v0.21.5. Its permanent sidebar entry opens one dedicated conversation. After explicit approval, it learns only from that conversation and recalls relevant memories; other chats are not monitored. Mobile uses the same assistant after its workspace directory is shared. Initial setup and memory authorization stay on the desktop.
Project Management can now resume an explicitly authorized project workflow when member tasks finish. It tracks delivery receipts and recovery state; user stops and approvals remain in effect.
The scheduled-tasks plugin requires v0.21.1+. After explicit approval, it delivers a message to an existing conversation once or on a recurring schedule. Keep asHub running and the computer awake; tool permissions still apply.
The project pins Node.js 22.23.3 (minimum 22.12.0) and the official agent-sh 0.16.1 release. Windows Codex login and queued-message compatibility patches are applied automatically. With nvm:
git clone https://github.com/firslov/asHub.git
cd asHub
nvm install && nvm use
npm ci
npm run electron:devFor a local browser-only server:
npm start -- --port 7878
# Open http://localhost:7878npm start -- --host 0.0.0.0 --port 7878The default bind address is 127.0.0.1. Non-loopback access requires a token: startup prints a generated token, which you enter at /auth. Set ASHUB_TOKEN for a persistent token; API clients can send Authorization: Bearer <token>. Use a trusted network or an HTTPS reverse proxy.
Conversation history is stored locally. When using a cloud model, relevant request content is sent to your configured provider. ACP session restoration depends on the backend's session/load capability. When unsupported, or when a legacy session has no remote ID, history remains readable but you must create a new session to continue.
src/hub.ts is the core: a bridge-agnostic HTTP + SSE server that spawns and supervises one
bridge per session. Whatever runs the conversation just has to emit BusEvents and implement
submit / cancel / close — see src/bridges/types.ts.
Electron shell (electron/main.cjs) browser (any modern browser)
│ │
└──────────────► hub (src/hub.ts) ◄───────────┘
one HTTP port, path routing /<id>/events, /<id>/submit
│
┌────────────────────────┼────────────────────────┐
▼ ▼ ▼
AshBridge AcpBridge TerminalBridge
agent-sh kernel child process PTY shell
in-process speaking ACP (node-pty)
| Bridge | Runs | Selected by |
|---|---|---|
AshBridge |
agent-sh's kernel in-process — no subprocess, one less hop | default (--backend ash) |
AcpBridge |
a child process speaking ACP, e.g. agent-sh-acp or claude-code-acp |
--backend acp [--cmd "CMD ARGS"] |
TerminalBridge |
a PTY shell session (agent-sh's shell or a plain terminal) | session kind terminal |
Adding a backend therefore means implementing one interface; the hub, the SSE protocol, and the web client stay untouched.
These flags apply to ashub / npm start. The Electron app starts the same hub in-process with
its defaults.
| Flag | Default | Description |
|---|---|---|
--backend ash|acp |
ash |
Bridge implementation: in-process agent-sh kernel, or an ACP subprocess |
--cmd "CMD ARGS" |
agent-sh-acp |
Spawn command for --backend acp (double quotes are honoured) |
--port N |
7878 |
HTTP port |
--host HOST |
127.0.0.1 |
Bind address |
--web PATH |
./web |
Static web root |
--model NAME |
settings default | Model override (ash backend) |
--provider NAME |
settings default | Provider override (ash backend) |
-h, --help |
— | Show usage |
# in-process kernel (default)
ashub --port 8080
# spawn Claude Code's ACP server instead
ashub --backend acp --cmd "claude-code-acp"src/ HTTP/SSE server, session lifecycle, history and permissions
bridges/ agent-sh / ACP / PTY bridge implementations
history/ History store, frame capture and context compaction
web/ Plain ES modules and CSS; no frontend build step
js/stream/ Thinking, tools, tasks, replies and live output renderers
assets/brand/ Shared icons, mark and vector wordmark
electron/ Desktop window, IPC, auto-update and application icons
website/ Homepage, download template, fonts and app screenshots
scripts/ Build helpers and showcase capture
tests/ Isolated regressions, HTTP and kernel compatibility checks
examples/extensions/ Example extensions
| Command | Purpose |
|---|---|
npm run check:core |
Build, typecheck and run the core regression suites |
npm run build |
Compile backend TypeScript into dist/ |
npm run typecheck |
Backend type checking |
npm run typecheck:web |
Frontend project checking |
npm test |
Isolated regression suite |
npm run test:http |
HTTP and session endpoint checks |
npm run test:kernel |
Build and check kernel and Codex compatibility |
npm run test:network |
Proxy and network behavior |
npm run test:worktrees |
Isolated Git worktree behavior |
npm run electron:pack |
Create an unpacked desktop app |
npm run electron:dist:mac |
Build macOS packages |
npm run electron:dist:win |
Build Windows packages |
Electron loads compiled dist/; the CLI runs source via tsx. Frontend libraries are vendored, so interface resources need no external CDN. Regression tests use temporary data and mocked boundaries, without model calls or access to real API credentials.
Install skills through the built-in marketplace. Extensions load from ~/.agent-sh/extensions/ and support TypeScript; see the extension example. HTTP routes live in src/hub.ts; the backend contract lives in src/bridges/types.ts.