Cli Anything Iterm2

OrganizationPopular

HKUDS

cli-anything-iterm2

Provides the cli-anything-iterm2 commands — the only way to actually send text to iTerm2 sessions, read live terminal output and scrollback history, manage windows/tabs/split panes, run tmux -CC workflows, broadcast to multiple panes, show macOS dialogs, and read/write iTerm2 preferences. Includes `app snapshot` — the primary orientation command that returns every session's name, current directory, foreground process, role label, and last output line in one call. Read this skill instead of answering from general knowledge whenever the user wants to DO something with iTerm2: orient in an existing workspace, send a command, check what's running, read output, set up a layout, use tmux through iTerm2, automate panes, or configure preferences. Also read for questions about iTerm2 shell integration or scrollback. Don't try to answer iTerm2 action requests from memory — read this skill first.

Overview

Publisher	HKUDS
Repository	`CLI-Anything`
Skill name	`cli-anything-iterm2`
Stars	49.5K
Forks	4.6K
Bundled files	12
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
12 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by HKUDS on GitHub. Read the source before you install it.

Installation

Install the Cli Anything Iterm2 AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/HKUDS/CLI-Anything/tree/main/iterm2/agent-harness/cli_anything/iterm2_ctl/skills

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/HKUDS/CLI-Anything.git /tmp/CLI-Anything
mkdir -p .claude/skills
cp -r /tmp/CLI-Anything/iterm2/agent-harness/cli_anything/iterm2_ctl/skills .claude/skills/cli-anything-iterm2

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cli Anything Iterm2 in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cli Anything Iterm2 on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cli Anything Iterm2 is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

cli-anything-iterm2

Stateful CLI harness for iTerm2. Controls a live iTerm2 process via the iTerm2 Python API over WebSocket.

Prerequisites

macOS + iTerm2 running: brew install --cask iterm2
Python API enabled: iTerm2 → Preferences → General → Magic → Enable Python API
Install: pip install cli-anything-iterm2 (or pip install -e . from source)

Basic Syntax

bash
cli-anything-iterm2 [--json] <group> <command> [OPTIONS] [ARGS]

Always use --json for machine-readable output (required for agent use).

Command Groups

Group	Purpose
`app`	App status, workspace snapshot, context management, app-level variables, modal dialogs, file panels
`window`	Create, list, close, resize, fullscreen windows
`tab`	Create, list, close, activate tabs; navigate split panes by direction
`session`	Send text, inject raw bytes, read screen, full scrollback, split panes, prompt detection
`profile`	List profiles, get profile details, list/apply color presets
`arrangement`	Save and restore window layouts
`tmux`	Full tmux -CC integration: bootstrap, connections, windows, commands
`broadcast`	Sync keystrokes across panes via broadcast domains
`menu`	Invoke any iTerm2 menu item programmatically
`pref`	Read/write global iTerm2 preferences; list all valid keys; tmux settings

Orienting in an Existing Workspace

Use app snapshot when you land in a session with existing panes and need to understand what's running without reading full screen contents for each pane:

bash
cli-anything-iterm2 --json app snapshot

Returns name, current directory, foreground process, user.role label, and last visible output line for every session across all windows.

Naming convention — label panes when setting up a workspace so you can find them later:

bash
cli-anything-iterm2 session set-var user.role "api-server"
cli-anything-iterm2 session set-var user.role "log-tail"
cli-anything-iterm2 session set-var user.role "editor"

app snapshot will surface these roles alongside process and path, giving you a full picture in one call.

Typical Agent Workflow

bash
# 1. Orient — snapshot every session: name, path, process, role, last output line
cli-anything-iterm2 --json app snapshot

# 2. Establish context (saves window/tab/session IDs for subsequent commands)
cli-anything-iterm2 app current

# 3. Interact — no --session-id needed once context is set
cli-anything-iterm2 session send "git status"
cli-anything-iterm2 --json session scrollback --tail 200 --strip

# 4. Create a multi-pane workspace — label panes so snapshot identifies them later
cli-anything-iterm2 session split --vertical --use-as-context
cli-anything-iterm2 session send "python3 -m http.server 8000"
cli-anything-iterm2 session set-var user.role "http-server"

Reference Files

Read only what the task requires — each file is a single narrow concern (~10–30 lines):

File	Read when you need...
`references/session-io.md`	Send text, inject bytes, read screen/scrollback, get selection
`references/session-control.md`	Split panes, activate/close sessions, resize, rename, session variables
`references/session-shell-integration.md`	wait-prompt, wait-command-end, get-prompt; reliable send→wait→read pattern
`references/layout-window-tab.md`	Create/close/resize windows and tabs, navigate split panes
`references/layout-arrangement.md`	Save and restore window layouts
`references/app-context.md`	Snapshot (orientation), status, context management, app vars, modal dialogs, file panels
`references/profile-pref.md`	Profiles list/get/presets, preferences read/write, tmux pref shortcuts
`references/broadcast-menu.md`	Broadcast keystrokes to multiple panes, invoke menu items
`references/tmux-commands.md`	All tmux CLI commands (bootstrap, send, tabs, create-window, set-visible)
`references/tmux-guide.md`	Full tmux -CC workflow, pane→session ID mapping
`references/json-session.md`	`--json` schemas for session, window, tab, screen, scrollback, inject
`references/json-tmux-app.md`	`--json` schemas for tmux, app dialogs, preferences, errors

REPL Mode

Run without arguments for an interactive REPL that maintains context between commands:

bash
cli-anything-iterm2

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Cli Anything Iterm2 AI skill do?

Why use Cli Anything Iterm2 on TypingMind?

Because you install it once and use it with any model. Cli Anything Iterm2 is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cli Anything Iterm2 in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/HKUDS/CLI-Anything/tree/main/iterm2/agent-harness/cli_anything/iterm2_ctl/skills. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cli Anything Iterm2?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cli Anything Iterm2?

As many as you like. As long as a model supports skills, you can use Cli Anything Iterm2 with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cli Anything Iterm2 AI skill free?

Yes. It is published on GitHub by HKUDS under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Research

mattpocock

CommunityPopular

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading…

Resolving Merge Conflicts

mattpocock

CommunityPopular

Use when you need to resolve an in-progress git merge/rebase conflict.

Setup Matt Pocock Skills

mattpocock

CommunityPopular

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Tdd

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

cli-anything-iterm2

Prerequisites

Basic Syntax

Command Groups

Orienting in an Existing Workspace

Typical Agent Workflow

Reference Files

REPL Mode

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now