zzunkie

Yardlet — Development skill for Claude Code

Development community

A native macOS app for running coding agents: Codex, Claude Code and other agent CLIs side by side in one window.

How to install Yardlet

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

What Yardlet does

A native macOS app for running coding agents: Codex, Claude Code and other agent CLIs side by side in one window.

Alternatives in Development

  • OpenSquirrel — For people who get distracted by agents 1.3k ★
  • Clarc — Native macOS client for Claude Code — a GUI desktop app built with SwiftUI 363 ★
  • Claude Code Skill — Persistent multi-engine coding session manager 326 ★

README

Yardlet

[![CI](https://github.com/zzunkie/yardlet/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/zzunkie/yardlet/actions/workflows/ci.yml)

A native macOS app for running coding agents. Codex, Claude Code and other agent CLIs open side by side in one window of projects and tasks, while each agent keeps its own agent loop, sign-in and session history.

Yardlet is written in Swift and SwiftUI; it is not a web view. It does not replace the agents or proxy their accounts: it starts the CLI you already use, with the account you already signed in to.

A Codex task in Yardlet: the conversation, with the changes, pull request checks, progress and settings beside it

What it does

  • One window for every agent. Codex, Claude Code, OpenCode, Cursor Agent, Antigravity CLI, Kimi Code, Grok Build, Pi and others share the same sidebar, conversation view, composer and approval cards. Controls stay in the same place; the choices and values come from each agent.
  • Sessions stay where the agent keeps them. Codex runs against your normal CODEX_HOME and Claude Code against its own store, so a session started in Yardlet resumes in the original app or CLI, and the other way round. Yardlet keeps only its own index, drafts and reading state.
  • Stop whenever you like. Yardlet writes nothing into the agents' own configuration; it hands them its tools when it starts them. Quit it or remove it, and each agent, its sign-in and its sessions are as they were, ready in the original app or CLI (see Uninstall).
  • Several accounts. Register more than one account per provider and start a task on the one with quota left; Yardlet shows each account's session and weekly limits.
  • Review the work. Diffs of the last turn, file restore and fork, a pull request tab with checks throug