Open-source control for local agent runs

Control local AI agents from anywhere

Find and resume Codex or Claude Code chats, or run other local agents through Generic CLI. DeskCue keeps full-access progress, artifacts, and steering reachable from another browser

native: codex / claude code · generic cli · local chats: ollama / lm studio
local run / checkout-refactorrunning
Agent on your machineWatch the run, then steer it
full access
3 files changedpreview :5173browser control
edited app/routes/checkout.tsxpreview listening on :5173

Approvals show only if the agent mode asks

DeskCue
Chats 4Attached 1Run 1
Interactive preview

Watch and steer local agent chats

Pick a local thread, inspect progress, then attach or resume when needed

Recent chats

All local chats in one place

Sample local chats
payment-flow~/projects/shop-app
LIVE IN CODEX
Latest update

Updated payment flow, changed 3 files, preview available on :5173

3 itemspreview :5173CODEX
Agent mode stays in the source chat; approvals appear only when requested
Apache-2.0
Credentials stay on your machine
Auth on by default
Early source-checkout alpha

Artifact trail

See the run without reopening the terminal

Transcript, activity, debug output, changed files, diff, live preview, and steering stay visible while the run continues

Status

running / done / failed / needs input

Logs

stream stdout, stderr, and agent transcript tail

Changed files

track workspace changes as the run evolves

Diff

review git diff and readable untracked text changes

Live preview

open a local port in desktop or mobile viewport

Steer

send instruction, stop, continue, or answer a prompt

Your machineworkspace, git, ports, agent process
DeskCue daemonlogs, status, diff, preview, stdin
Phone or browsermonitor progress and steer

What runs where

One local loop, three surfaces

Your agent and workspace stay on your machine. The DeskCue daemon observes the run and exposes a paired browser/PWA surface for review and steering

  • Apache-2.0 and self-hostable
  • Auth enabled by default with per-device pairing
  • Bring your own agent accounts and local models
  • Approve/reject appears only when the selected agent mode asks

Current local support

DeskCue starts with the tools already on your machine

Codex

local source sessions, status, transcript, resume path

Claude Code

local source session discovery and continuation path

Generic CLI

start other local agents in a workspace, stream output, and send input

LM Studio

DeskCue-owned local chats with workspace context and a local model endpoint

Ollama

DeskCue-owned local chats with workspace context and a local model endpoint

Browser access and notifications

Browser first, native apps later

DeskCue reaches your phone through the browser dashboard today. Route approval-needed, session finished, session failed, and source-agent turn finished signals through Web Push or your preferred provider

Web Push
ntfy
Gotify
Telegram
Webhook
More providers planned

Current start path

No installer yet, start from source

The current supported path is intentionally simple: clone the repo, install dependencies, and run the local service with npm; installers, packaged desktop flows, and native mobile apps can come later

# source checkout
$ git clone https://github.com/AleksandrKornev/DeskCue.git
$ cd DeskCue && npm install
$ npm run start
# open the dashboard from browser or phone
Open GitHub

Cloud access

Cloud Preview first; no paid plans yet

Cloud Preview keeps a bounded session-metadata projection. After local opt-in, DeskCue reads, Files, Diff, control, realtime, and Preview pass transiently while the daemon is online; Remote DeskCue payloads are not stored. Paid plans and checkout are not available, and the source version keeps the complete local loop

Self-hostavailable now
$0

Run DeskCue locally from source; no hosted relay required

  • browser dashboard
  • local agents and runtimes
  • logs, diff, preview
  • notifications via local providers
Start from source
Cloud Previewfree preview
$0

Connect your daemon for durable session metadata and opt-in transient Remote DeskCue access

  • durable bounded session metadata
  • opt-in transient Files and Diff
  • opt-in transient control and realtime
  • isolated transient Preview
Create free account
Soloplanned
Later

For solo developers who want DeskCue reachable beyond the LAN

  • persistent remote access
  • notification routing
  • session history sync
  • private preview tunnels
Studioplanned
Later

Future paid tier for heavier personal workflows and pairing needs

  • multiple machines
  • larger artifact windows
  • advanced routing
  • priority cloud limits