Your workspace across devices

Where everything runs

• Koyd Server owns agent execution, durable queues, swarm supervision, files, Git, terminals, databases, memory, and app backends.
• The React PWA presents the workspace and keeps local presentation state, drafts, and device connection credentials.
• A release includes the server, Rust core, Node runtime, dependencies, memory model, and PWA assets.
• The marketing website provides documentation, downloads, and update metadata. It does not relay your project sessions.

Run an instance on your laptop, workstation, or a VPS. Moving between clients changes how you access it; it does not move your files or synchronize separate servers.

Connect and switch instances

Each server has its own identity, data directory, configuration, and paired devices. Use the connection manager to pair another server and select the workspace you want. Give instances recognizable names so you know which machine a command will affect.

Good to know · There is no automatic project or credential synchronization between instances.

The current interface

The workspace combines project and session navigation, the conversation and composer, and the panels relevant to the selected task. Panels adapt to available space. On narrow screens, use the navigation controls to reach the project, sessions, and tools.

Koyd Dark is the official default theme. Supported alternative themes are available through settings; the connection screens and workspace follow the active instance’s appearance.

Your Koyd Apps on each device

Open Apps to find tools saved on the selected instance. On desktop, Open app requests a separate window. Open here keeps it inside Koyd; phones, tablets, narrow screens, and blocked windows use this view automatically. Back to Koyd returns to the existing chat and draft.

App backends and durable data stay on the paired server. The browser or installed PWA needs a live connection for server features. Switching servers changes which app library and data you are using.

Readable technical content

Supported rendered diagrams and document views help explain results alongside code and messages. Inspect the underlying text or source when you need precise details or want to reuse a result.

Offline, drafts, and reconnects

The installed PWA can cache its app shell. That lets the interface open offline, but server commands still require a connection. Unsent drafts stay in the client. Reconnect to recover the server’s current state and transcript.

Closing a tab does not cancel server work. Stopping the server does end active agents, terminals, and browser sessions. Saved data and device pairings persist.

Move a server carefully

To migrate to another machine, stop the instance, back up its data and configuration, and install the matching package on the destination. Keep the intended project paths and provider/network requirements in mind. Never run two live servers from the same data directory.

Good to know · The bundled runtime is specific to its operating system and processor. Portable does not mean a Windows binary runs on Linux, or that copying only the PWA copies your work.