One coding agent, three clients

Open the same chats from the desktop app, terminal, or browser. Built in Rust, open source, with chat history stored locally.

curl -fsSL https://raw.githubusercontent.com/DroBov1Tya/dusk_code/main/install.sh | sh

macOS arm64 and Linux x86_64 / arm64 · MIT · Releases

The duskcode desktop app showing a project chat and its task list

One core, three clients

They draw the same threads over one protocol, so a chat started in one opens in another, and a feature lands once.

The subagents window: agents by the zone of their work

Desktop duskcode-gui

Chats and projects, a file viewer and editor, your own terminal in a panel, subagents and the arbiter in windows of their own.

The terminal client: the rail, the steps of a turn and the answer

Terminal duskcode

Full screen in any terminal, 24-bit colour, keyboard and mouse. Runs on a server over SSH, and headless with duskcode run.

The web client: a chat with the task list beside it

Browser duskcode --web

The same chats in a browser, served by the core. Bound to this machine unless you open it to your network.

What it does

The work of a coding agent, with the parts you may want to read or change kept as plain files.

Works in your project

Reads, searches and edits files, runs commands in the foreground or as background jobs, and keeps a task list while it goes.

Delegates

Specialist agents by role, several at once, each in a thread of its own. An arbiter can answer their approval requests under your rules.

Asks first

Ask, sandbox, arbiter or full access, set per chat. An approval nobody can give is denied.

Extends

Skills loaded when a task needs them, MCP servers for tools, plugins for providers, hooks and platforms such as a Telegram bot.

Remembers in the open

Notes per project and about you are Markdown files. A temporary chat lives in memory and leaves nothing on disk.

Goes the distance

Goals with acceptance criteria, scheduled runs, context compaction, forks from a summary and undo to an earlier message.

Any model, with or without a key

OpenAI, Anthropic and Google with an API key; any server that speaks the OpenAI API; local models on localhost. Or sign in with ChatGPT and use the models of your plan:

  1. The browser asks, not the app. duskcode opens OpenAI's sign-in page and listens on 127.0.0.1. It never sees your password.
  2. OpenAI issues this install its own client ID and sends the browser back with a one-time code. Authorization code with PKCE; there is no client secret.
  3. The identity is checked. Signature against OpenAI's published keys, issuer, audience, expiry and nonce, and that use of the plan was granted.
  4. Requests go to the Responses API with storing switched off. The record is kept in the system keychain and works only with api.openai.com.

A Claude subscription cannot be used this way: Anthropic allows signing in with a Claude account only in its own apps. Claude models work with an API key.

Local by default

No duskcode account or hosted chat storage. Tracing is off by default. Model requests go to the provider you configure.

Secrets in the keychain

Secrets are kept in the system keychain. Without it, provider API keys stay in a private local config file.

Network connections

Duskcode connects to the providers and servers you set up, checks GitHub for updates, and fetches the signed catalog when you open the Workshop.

Inside your projects

Files and git only in saved projects; paths are canonicalized, and .. or a symlink that leads out is refused.

Read it yourself

The MIT-licensed source and dependency lockfile are public.

Say thanks

duskcode is free and has no paid tier. If it saves you time, a coffee is welcome. Issues and pull requests help as much.

Bitcoinbc1q636n7dg4kwjqn0tm4v5vlxfwzydqgte4423xkz
Litecoinltc1q0xdfq0ze6f2cqdufgnnm3p3fls5km9qvjj2vkd