Codypendent

The problem

A coding session should survive switching interfaces. Conversation history, tool execution, approvals and repository state need one owner rather than separate implementations in every client.

What I’m building

Codypendent centres the product on a Rust daemon. Terminal, desktop and IDE clients use the same sessions and execution machinery. The repository includes a TUI, Tauri desktop application, CLI, web client and IDE integrations.

Design decisions

The daemon owns session state and tool execution. Clients concentrate on presenting that state and collecting input. Git worktrees give parallel work separate checkouts; approvals and sandbox controls sit at the execution boundary.

Recovery matters as much as the initial happy path. Draft retention, interrupted streams, tool-card readability and session restoration are part of the application work.

Evidence and status

The public repository contains the clients, daemon, protocol and release history. Development covers session continuity, approvals, worktree isolation and recovery across the interfaces.

Explore

Start with the architecture, the CLI and TUI user guide, or the releases for available builds.