ZyxWorks

Agent Office — Communication skill for Claude Code

Communication community

Build agents with agents, in one tmux window.

How to install Agent Office

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

What Agent Office does

Build agents with agents, in one tmux window. Several coding-agent sessions side by side, each in its own git worktree, plus a shell, a file editor that follows it, and a chat pane wired to the agent you built. Claude Code, Codex or any CLI. Close the window and nothing dies. ~850 lines of zsh, no daemon.

Alternatives in Communication

Lark Coding Agent Bridge — Bot that bridges Feishu/Lark messenger with a local Claude Code or Codex CLI 2.4k ★
Claudix - Claude Code For VSCode — by Haleclipse - A VSCode extension that brings Claude Code directly into your editor with interactive chat int 1k ★
Openab — A lightweight, secure, cloud-native ACP harness that bridges Discord and any ACP-compatible coding CLI 321 ★

README

Agent Office

Several agents. One window.

Each one in its own git worktree. The one that has stopped and is waiting on you says so, on its own border, without being asked.

[![CI](https://github.com/ZyxWorks/agent-office/actions/workflows/ci.yml/badge.svg)](https://github.com/ZyxWorks/agent-office/actions/workflows/ci.yml) [![Licence: MIT](https://img.shields.io/badge/licence-MIT-c9903f)](LICENSE) ![Platform: macOS, Linux and WSL2](https://img.shields.io/badge/platform-macOS%20%7C%20Linux%20%7C%20WSL2-6a6c77) ![No daemon](https://img.shields.io/badge/daemons-0-6a6c77)

**Several coding agents side by side, each in its own git worktree, plus shells and a file editor, in one window.** "Your turn" and how full each context window is, right on the border. Claude Code out of the box, Codex, a local model, or any other CLI — one more line in `OFFICE_AGENTS`.

[**The product page**](https://zyxworks.github.io/agent-office/) · [Our other tools](https://zyxworks.com/) · [What we do for companies](https://zyxworks.com)

office on

┌──────────────┬──────────────┬──────────────┐
│ 1 CLAUDE     │ 2 CODEX      │ 3 SHELL      │
│              │              │              │
│              │              │              │
└──────────────┴──────────────┴──────────────┘

`office on` opens ONE pane that asks what it should be: any `OFFICE_AGENTS` entry, a shell, or the file editor. `Ctrl-Space n` asks the same question for every pane after that, and the grid re-fits itself — three across at most, two down, six in all. Park a pane with `Ctrl-Space x` and it keeps running, listed at the top of that same menu as `back: `; drag a pane's title onto another to move it there; the rest shift along.

Closing the window kills nothing: `office on` puts you back exactly where you were, panes and all.

**New to running an agent in the terminal?** Start with **[GETTING-STARTED.md](GETTING-STARTED.md)**: what each pane is, how to move around, and how to get back