typescript
- strict mode is enabled in `apps/emdash-desktop/tsconfig.json` - always use explicit types, do not use `any` - prefer module imports at the top of the file, never use require() - single `tsconfig.json` (in `apps/emdash-desktop/`) for all app targets (main, preload, renderer,
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
- strict mode is enabled in `apps/emdash-desktop/tsconfig.json` - always use explicit types, do not use `any` - prefer module imports at the top of the file, never use require() - single `tsconfig.json` (in `apps/emdash-desktop/`) for all app targets (main, preload, renderer,
Agent definition
typescript.mdTypeScript And React Conventions
TypeScript
- strict mode is enabled in `apps/emdash-desktop/tsconfig.json`
- always use explicit types, do not use `any`
- prefer module imports at the top of the file, never use require()
- single `tsconfig.json` (in `apps/emdash-desktop/`) for all app targets (main, preload, renderer, shared)
Renderer
Paths are relative to `apps/emdash-desktop/`.
- functional React components and hooks
- app shell and the modal/view registries under `src/renderer/app/`
- feature UI under `src/renderer/features/<feature>/`
- shared infrastructure under `src/renderer/lib/` (IPC client, modal and layout
systems, commands, PTY frontend, providers, hooks, stores, UI primitives)
Naming
- components: PascalCase
- hooks: `useX` camelCase or existing patterns like `use-toast.ts`
- tests: `*.test.ts`
Emdash is the Open-Source Agentic Development Environment (🧡 YC W26). Run multiple coding agents in parallel. Use any provider.
Repo: generalaction/emdash
Other agents on emdash.
- acp-runtime
The ACP runtime is the domain service that serves the ACP API contract. It owns the host-scoped dependencies needed to run provider ACP sessions, but it should not mix cross-session routing with per-session state projection.
Open agent - main-process
The main process is organized into domain modules under `src/main/core/`. Each domain typically has a `controller.ts` (RPC handlers) and service/implementation files.
Open agent - overview
All paths are relative to `apps/emdash-desktop/`.
Open agent - renderer
All paths are relative to `apps/emdash-desktop/`.
Open agent - shared
- Agent/provider DTOs: - `src/shared/core/agents/agent-payload.ts` - provider metadata and capabilities are sourced from `packages/plugins/src/agents/registry.ts` - IPC primitives: - `src/shared/ipc/rpc.ts` — typed RPC router, controller, and client - `src/shared/ipc/events.ts`
Open agent - workspace-server
The Workspace Server (`apps/workspace-server/`) is a Node daemon that runs on a remote machine and exposes workspace runtimes (git, files, deps, ACP, …) to Emdash clients over the `@emdash/wire` protocol. Clients connect over an SSH-forwarded Unix socket; the daemon is
Open agent