Local-first workbench for agent-assisted software development.
Aldunis Code gives you one loopback-bound interface for repositories, worktrees, conversations, tool approvals, and diffs. Provider CLIs (Claude Code, Codex, Shikigami, and reviewed ACP adapters) run as local subprocesses under an explicit permission model. The browser never receives provider credentials or unrestricted filesystem access.
Status: early / pre-release. Suitable for local development and review, not unattended production use.
Most coding agents are either a terminal session or a cloud IDE tab. Aldunis Code is a local host + web UI that:
- binds conversations to a canonical repository and worktree
- normalizes multi-provider events into one conversation model
- requires scoped, inspectable approval for mutating tools
- keeps secrets and state on the machine, not in the browser
| Product | Role |
|---|---|
| Aldunis Code (this repo) | Local workbench, providers, approvals, diffs |
| Sekai Chisei | Governance, policy, budgets, evidence, audit |
| Tenkai | Releases, environments, delivery, recovery |
Cross-product screens consume authenticated contracts only. They never share databases or treat cached UI projections as authority. Sekai / Chisei / Tenkai appear in the product switcher only when configured (see getting started).
Requirements: Node.js 22.12+, npm, Git, and a local Git repository to open.
npm ci
npm startOpen http://127.0.0.1:4174.
For development, run the API host and Vite in separate terminals:
# Terminal 1
npm run cli -- serve --port 4175
# Terminal 2
npm run devOpen http://127.0.0.1:4174; Vite proxies API requests to the host on port 4175.
Verify:
npm test
npm run check
npm run buildNightly desktop releases are opt-in prereleases. When Windows Authenticode credentials are not configured, the nightly workflow may publish an unsigned Windows installer and labels that limitation in the release notes. Stable releases remain fail-closed and require signed Windows and macOS packages. See desktop distribution for the signing requirements and update-channel behavior.
Full install, providers, remote access, and desktop packaging: docs/getting-started.md
The host command reference, including structured startup and remote-auth commands, is in docs/cli.md.
Contributions are welcome. Start with CONTRIBUTING.md, use the issue templates for bugs and features, and report vulnerabilities privately through SECURITY.md. The project is pre-release, so proposals that reduce unsafe authority, clarify provider boundaries, or improve deterministic verification are especially useful.
| Doc | Audience |
|---|---|
| Documentation index | Map of all docs |
| Getting started | Install, run, first conversation |
| Architecture | Topology, ownership, security invariants |
| Providers | Claude, Codex, Shikigami, ACP adapters |
| Automations | Scheduled prompts into existing threads |
| Local data | State directory, history, preferences |
| Remote workbench | Tailscale / LAN remote access |
| Work lifecycle | Issues, PRs, review |
| Decisions | Accepted design decisions |
| Contributing | How to contribute |
| Security | Vulnerability reporting |
| AGENTS.md | Repository-specific engineering rules for agents |
MIT — Copyright (c) 2026 Aldunis contributors.