Getting Started

Start with Cordy Desktop, the local workspace for repositories, terminals, CLI agents, project tools, notes, and a built-in browser.

Cordy Desktop is a local-first workbench for a repository. It combines workspaces, supervised terminal tabs, external CLI agents, file and Git tools, notes, search, diagnostics, and a manual built-in browser.

Cordy does not embed its own chat model. CLI agents use their own configuration, accounts, and provider connections. Cordy renders their terminal output and infers a small set of activity states.

Source and the repository tag are at 0.4.0. Its GitHub Release is still a draft. The latest published Release is 0.3.0, with one verified Windows x64 asset: cordy-Setup-0.3.0.exe.

First workflow

  1. Install the published Windows build, or run matching source.
  2. Choose Add repository, drop a repository folder, or press Ctrl+Shift+O.
  3. Select the project and create a workspace. The current creation flow makes a project-root workspace in one step.
  4. Open a terminal tab or launch an installed agent preset.
  5. Use Project Tools to edit files, search the project, inspect Git changes, or read the commit graph.
  6. Keep task notes in the workspace notebook, and use the browser for manual web work.

What a workspace contains

  • one code target, currently the imported project root for newly created workspaces;
  • terminal tabs and split panes, with shell and agent processes owned by the Rust runtime;
  • a Markdown notebook stored locally;
  • open file tabs and layout state;
  • project-wide Files, Search, Changes, and Graph views.

Existing worktree-backed workspace records remain supported and show their worktree path. The current UI does not create a new worktree when you press New Workspace.

Durability boundary

Closing the main window to the tray keeps the runtime and live PTYs running. A renderer reload reattaches to the live sessions. A full quit ends the processes; on next launch Cordy restores a local terminal screen/history snapshot above a fresh shell. See Terminal and Runtime.

Next