Tech Stack - Monad

A quick-reference map of every tool and library in the repo, organized by concern.

Runtime & language

Tool	Role
Bun	JS runtime, package manager, bundler, test runner — replaces Node/npm/jest/webpack entirely
TypeScript 7	Language and fast native type-checker; strict mode throughout

Monorepo

Tool	Role
Turborepo	Task graph, remote caching, parallel builds across `apps/` and `packages/`
mise	Pins the toolchain, loads the per-worktree `.env.local`, and owns the `quality:*` task graph
Syncpack	Keeps package version ranges in sync across the monorepo
Knip	Reports unused files, exports, and dependencies (check-only — never `--fix`)
Bun workspaces	Module resolution within the `@monad/*` scope

Code quality & git hooks

Tool	Role
Biome	Linting + formatting (replaces ESLint + Prettier)
Lefthook	Git hooks runner — runs fast staged-only fixes and checks
Commitlint + Commitizen	Enforces Conventional Commits on every commit message
Rulesync	Compiles committed `.rulesync/rules/` into gitignored local targets for supported agents

Backend daemon (`apps/monad`)

Tool	Role
Elysia	HTTP + WebSocket server (runs on `Bun.serve` under the hood)
Drizzle ORM + drizzle-kit	Type-safe SQL query builder; schema in `apps/monad/src/store/db`, migrations in `apps/monad/drizzle`
`bun:sqlite`	Embedded SQLite — primary persistence layer (no external DB required)
`Bun.redis`	In-process KV store (`apps/monad/src/store/kv`)
Zod v4	Schema validation at all wire boundaries (HTTP/WS/disk)
OpenTelemetry	Tracing + metrics exported via OTLP (OpenInference semantic conventions)
@modelcontextprotocol `core`/`client`/`server`	MCP client (stdio + HTTP transports) and the agent-facing MCP server
@agentclientprotocol/sdk	ACP server — exposes the daemon as an ACP agent to editors
@a2a-js/sdk	A2A server — exposes an agent as a standard Agent2Agent agent
mem0ai	Optional semantic-memory backend (local Qdrant managed by the daemon)

AI / agent layer (`apps/monad/src/agent`, `@monad/atoms`)

Tool	Role
Vercel AI SDK	Used internally by the first-party provider adapters in `@monad/atoms`
Provider atoms	Model backends registered through `@monad/sdk-atom`; the contract itself is ai-sdk-free

Web UI (`apps/web`, `@monad/ui`)

Tool	Role
Vite (rolldown build)	Development server and production SPA build (`out/`)
TanStack Router	Type-safe file-based client routing and generated route tree
React 19	UI framework; React Compiler enabled
Tailwind CSS v4	Utility-first CSS; PostCSS pipeline
Redux Toolkit + React-Redux	Global client state via `@monad/client-rtk` (sessions, messages, config)
Streamdown + Shiki	Incremental Markdown rendering and syntax highlighting (in `@monad/ui`)
Hugeicons	Icon set — named imports only, never the barrel
`@monad/i18n`	In-house message catalogs (`packages/i18n/src/locales/<lng>/<namespace>.json`); language packs ship as `locale` atoms

TUI (`apps/tui`)

Tool	Role
Ink	React renderer for the terminal
Zustand	Local TUI state (lighter than Redux for a single-process terminal)
Redux Toolkit + React-Redux	Shared session/message state (mirrors the web layer)

CLI (`apps/cli`)

Tool	Role
CAC	Lightweight command-line argument parser

Sandboxing (`@monad/sandbox`, `@monad/sandbox-vm`)

Tool	Role
Seatbelt / bubblewrap + Landlock + seccomp / AppContainer	Per-OS lightweight launchers, compiled from `apps/monad/native/sandbox-launcher`
Local egress proxy	Muxed HTTP CONNECT + SOCKS5 domain filtering, optional TLS termination
QEMU/KVM · vfkit · Hyper-V	Optional VM backend with a Go guest agent (`packages/sandbox-vm/native`)

Testing

Tool	Role
`bun test`	Unit and integration tests; E2E tests run over both TCP and Unix-socket transports
Playwright	Browser-based E2E for the web UI (path configured via `PLAYWRIGHT_BROWSERS_PATH`)

Release & CI

Tool	Role
release-please	Automated changelog + version bump PRs from Conventional Commits
GitHub Actions	CI matrix: macOS, Linux, Windows; Docker musl stage for static builds

Key constraints

No Node.js — everything runs on Bun. Don’t introduce node, ts-node, jest, webpack, express, pg, ioredis, better-sqlite3, or ws.
No external DB at runtime — SQLite + Bun KV only; the daemon must work offline with zero infra.
Schema-first at boundaries — every HTTP/WS/disk boundary uses a Zod schema as the single source of truth; never cast external data.