Aeroric: Desktop Workspace for AI Coding Agents

Run Claude Code, Codex, and custom agents across projects with live terminals, task tracking, Git, SSH, WSL, SFTP, Docker, database tools, Skill Hub, Markdown docs, quick notes, and release workflows in one lightweight desktop app.

中文文档

Current release: v1.3.8 · Stack: React 19 / Tauri 2 / Rust · Platforms: macOS / Windows / Linux

Aeroric is built for agent-first development, where multiple AI coding tasks may run at the same time across local repositories, remote machines, and operational environments. Instead of switching between terminal tabs, editors, Git clients, Docker tools, database consoles, release pages, and session logs, Aeroric keeps the workflow in one desktop workspace: start work, watch terminal output, inspect files, edit code and Markdown, keep quick notes, run scripts, review changes, and publish releases.

Aeroric does not replace Claude Code or Codex. It calls the native CLIs and adds a desktop control layer around them: multi-project navigation, permission-aware task launch, PTY-backed terminals, automatic session discovery, file browsing, LSP-backed editing, SFTP/SSH operations, Git review, Docker visibility, database utilities, local task persistence, and release coordination.

• Run recursive agent workflows: start tasks, inspect output, branch into follow-up actions, and keep the evolving context visible.
• Manage project workspaces: open local or remote projects and organize tasks, files, Git state, and runtime status around each repository.
• Run Claude Code, Codex, and custom agents: create tasks, choose permission modes, stream PTY output, provide interactive input, resume sessions, and cancel work when needed.
• Browse, edit, and execute project files: inspect repository files, modify scripts, run commands, use language-server features, and keep file operations close to the agent conversation.
• Read and edit Markdown: switch between rendered reading mode and source editing mode for README files, plans, specs, generated reports, and local knowledge notes.
• Use IDE-grade project tools: search and replace, inspect diagnostics, jump through symbols, run tests, debug with DAP, manage run configurations, and preview local web apps.
• Keep quick notes: write Markdown or rich text notes for task clues, command snippets, release checks, and temporary ideas.
• Operate development infrastructure: view Docker containers and images, manage ports, use SFTP/SSH tools, and inspect SQLite, MySQL, PostgreSQL, Redis, and MongoDB resources through DBX-powered tooling.
• Work inside WSL on Windows: detect installed distributions, manage WSL configuration, open projects on the Linux filesystem, and run terminals, agent tasks, and Git operations inside the selected distribution.
• Keep skills and release work close: browse local Skill Hub content, review diffs, stage files, commit, push, and manage release pages.
• Track usage, sessions, and notifications: discover Claude Code/Codex JSONL sessions, inspect token/tool-call metrics, and keep long-running work observable.

Tasks can launch, stream output, branch into follow-up actions, and remain visible as they evolve, which fits multi-step debugging, code generation, and release preparation.

The project page keeps task lists, agent controls, file tools, Git context, and workspace actions together so each repository can be managed without losing its state.

Claude Code and other agents run in PTY-backed terminals with live output, interactive input, session controls, copy behavior, font controls, file context, and IME-safe text entry.

Aeroric keeps file browsing, source edits, and command execution in the same workflow, which is useful for agent-assisted debugging, script iteration, and repository maintenance.

Rendered Markdown preview is built into the file viewer, making README files, plans, specs, and generated reports easy to review before committing them.

Markdown files can also be edited directly with syntax-aware source mode, so documentation updates stay inside the same project workspace.

Quick notes support Markdown and rich text content for task clues, command snippets, release checks, and temporary ideas.

The Docker page lists containers and images with status, runtime, port mappings, and refresh controls for local development and deployment checks.

SFTP tools keep remote file transfer and remote project inspection available next to local project work, which reduces context switching during deployment or server-side fixes.

SSH connections can be managed from Aeroric so remote shells, project operations, and agent-assisted terminal work stay in the same desktop environment.

On Windows, WSL distributions are treated as first-class execution environments. Aeroric detects the installed distributions, reads their login-shell environment and agent status, and can open a project that lives on the Linux filesystem instead of accessing it as a Windows share.

• Settings → WSL: check wsl.exe availability, list distributions with state and WSL version, pick a default distribution, inspect the login-shell environment (sensitive values are masked until revealed), override the claude / codex executable and config paths, edit %USERPROFILE%\.wslconfig and /etc/wsl.conf, and restart WSL after a confirmation prompt.
• Open WSL Project: the "Open project" menu offers a WSL entry that asks for a distribution and an absolute Linux path (for example /home/dev/app). The path is validated inside the distribution before the project is created, and the project is persisted as wsl://<distribution><linux-path>.
• Terminals and agent tasks: shells and Claude Code / Codex / custom agent tasks run inside the selected distribution through your Linux login shell, with the same PTY streaming, interactive input, resume, and cancel behavior as local tasks.
• Files and Git: file browsing, editing, project configuration, and Git status/stage/commit/history for WSL projects execute directly in the distribution.

The first WSL release intentionally leaves out LSP features, the test explorer, DAP debugging, web preview, Docker, database tools, Conda, task worktrees, and attachment upload. Those panels are disabled for WSL projects, while local and SSH projects keep their full capability set.

The Skill Hub makes local skill libraries visible and editable, helping agents reuse team workflows, coding conventions, and specialized procedures.

Database-oriented project utilities are grouped in the sidebar so application state and supporting resources can be inspected without leaving the workspace.

The release workflow helps collect version context, review publish state, and keep release work close to the code changes that produced it.

Download the installer for your platform from the GitHub Releases page. Each desktop release is expected to publish macOS DMG, Windows NSIS/MSI, Linux DEB/RPM, and SHA256SUMS.txt checksum assets.

Install Claude Code and/or Codex before using agent tasks in Aeroric. Published macOS installers are Developer ID signed and notarized; published Windows installers are Authenticode signed.

Local builds need Node.js 24, pnpm 9, Rust stable, the Tauri platform dependencies for your OS, and a sibling DBX checkout that satisfies src-tauri/Cargo.toml:

git clone https://github.com/t8y2/dbx.git ../dbx
git -C ../dbx checkout 8559aec8bce4efeb4f52080da8ab1839733ef45b
./scripts/prepare-dbx.sh

The preparation script applies Aeroric's reviewed DBX dependency/security updates from patches/dbx-security.patch. It is idempotent and is also run by the checks and desktop-release workflows.

pnpm dev            # Start Vite dev server on port 1420
pnpm build          # Type-check and build frontend
pnpm lint           # Run ESLint
pnpm test           # Run Vitest
pnpm tauri dev      # Start the desktop app
pnpm tauri build    # Build production desktop bundles

The frontend is React 19 + TypeScript + Vite. The desktop shell is Tauri 2 + Rust. Backend commands live in src-tauri/src/, and most application state is owned by src/App.tsx and persisted through Tauri storage commands.

For a tagged release such as v1.3.8, keep package.json, src-tauri/tauri.conf.json, and src-tauri/Cargo.toml on the same version before pushing the tag. After the desktop workflow finishes, verify the release contains:

• Aeroric-X.Y.Z-1.x86_64.rpm
• Aeroric_X.Y.Z_aarch64.dmg
• Aeroric_X.Y.Z_amd64.deb
• Aeroric_X.Y.Z_arm64-setup.exe
• Aeroric_X.Y.Z_arm64_en-US.msi
• Aeroric_X.Y.Z_x64-setup.exe
• Aeroric_X.Y.Z_x64.dmg
• Aeroric_X.Y.Z_x64_en-US.msi
• SHA256SUMS.txt

The release workflow intentionally fails when signing credentials are absent and REQUIRE_SIGNED_RELEASES=true is set. By default, unsigned installers are built when credentials are missing. Configure these GitHub Actions secrets before tagging:

• macOS: APPLE_CERTIFICATE, APPLE_CERTIFICATE_PASSWORD, APPLE_ID, APPLE_PASSWORD, APPLE_TEAM_ID, and KEYCHAIN_PASSWORD
• Windows: WINDOWS_CERTIFICATE and WINDOWS_CERTIFICATE_PASSWORD

WINDOWS_TIMESTAMP_URL may be set as a repository variable to override the default DigiCert timestamp service. The workflow verifies Authenticode signatures, macOS code signatures, and the stapled notarization ticket before it uploads release artifacts.

Aeroric builds on excellent open-source projects including Tauri, React, xterm.js, CodeMirror, and Shiki.

Special thanks to hanshuaikang/nezha, t8y2/dbx, stablyai/orca, and farion1231/cc-switch for open-source work that informs Aeroric's agent workspace, database tooling, mobile experience, and agent configuration workflows.

Community recognition: LINUX DO.