remote-development
- `src/main/core/ssh/` — connection management, credentials, config parsing - `src/main/core/pty/ssh2-pty.ts` - `src/main/core/fs/impl/ssh-fs.ts` - `src/main/core/terminals/impl/ssh-terminal-provider.ts` - `src/main/utils/shellEscape.ts`
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.
- `src/main/core/ssh/` — connection management, credentials, config parsing - `src/main/core/pty/ssh2-pty.ts` - `src/main/core/fs/impl/ssh-fs.ts` - `src/main/core/terminals/impl/ssh-terminal-provider.ts` - `src/main/utils/shellEscape.ts`
Agent definition
remote-development.mdRemote Development
Main Files
- `src/main/core/ssh/` — connection management, credentials, config parsing
- `src/main/core/pty/ssh2-pty.ts`
- `src/main/core/fs/impl/ssh-fs.ts`
- `src/main/core/terminals/impl/ssh-terminal-provider.ts`
- `src/main/utils/shellEscape.ts`
Current Model
- remote projects are backed by SSH connections
- remote worktrees live under `<project>/.emdash/worktrees/<task-slug>/`
- remote PTYs stream agent shells back to the renderer
Authentication And Storage
- SSH credentials are managed through the SSH services and OS-backed secret storage
- host key handling is implemented under `src/main/core/ssh/`
Rules
- treat all shell construction as security-sensitive
- use shared SSH and shell-escaping helpers instead of ad hoc quoting
- confirm whether a feature is local-only before assuming parity on remote projects
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