JPITSG

Puppy — Development skill for Claude Code

Development community

One persistent web console for every coding agent you run.

How to install Puppy

This entry records only its repository, not the path inside it, so there is no exact command to give. Open JPITSG/Puppy and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Puppy does

One persistent web console for every coding agent you run. Drive Claude Code, Codex and OpenCode from your browser or phone across every machine you own: durable sessions and queues, steering and side questions, parallel tasks in Git clones, shared terminals, managed browsers, VNC, full-history search. Python + aiohttp + SQLite.

Alternatives in Development

  • Nexting — Remote control for Claude Code, Codex, Grok, and Cursor on Mac or PC 1.3k ★
  • Agentlas Login — Sign this machine into Agentlas (opens the browser sign-in window) 1.1k ★
  • Herdrm — Native macOS console for herdr — all your coding agents and their live terminals, across devices 635 ★

README

Puppy console on a desktop: session sidebar, running task tabs, a transcript with tool cards, a compact composer, and a full-history search pane

Puppy 🐾

One persistent web console for every coding agent you run.
Drive Claude Code, Codex and OpenCode from your browser, from your phone, across every machine you own.

Quick start · The tour · Multi-machine · Settings · Security · Tests · License


Puppy runs the official `claude`, `codex` and `opencode` CLIs for you, turns their raw event streams into one clean, searchable transcript, and keeps that transcript and every session forever in its own SQLite database. Close the laptop, open your phone, and the same conversation is waiting for you, with your half-typed prompt still in the box.

There is no build step, no npm, no daemon besides Puppy itself: Python 3.9+, `aiohttp`, and the agent CLIs you already have.

Why Puppy

  • Every engine, one console. Claude Code, Codex and OpenCode sessions sit side by side. A session can switch engines at any time and the new engine picks up the story from a transcript handoff.
  • Talk to the agent while it works. Steer a running turn, ask it a side question it answers without derailing its work, queue the next prompts, approve or deny tool calls, all from the same box.
  • Tasks in parallel. Spin off tasks that work in isolated Git clones of your project, review their diffs, and apply the winners to your working tree.
  • A fleet, not a box. Pair other machines as backends, run sessions there, attach shared terminals and managed browsers on any of them, and let a