En

@0xkahi/pi-arsenal

Pi Multi-Tool Extension: Non-Blocking tmux Popup Editor

开发流程 开发AI应用调试复杂代码管理本地文件编写业务代码 通用 ★ 235 Updated 2026-08-02

Install & Use

Copy this prompt and send it to your AI assistant (Claude / Cursor / TRAE / Codex / WorkBuddy etc.) to auto-install:

Help me install this AI Skill: @0xkahi/pi-arsenal.
It is used for: Pi Multi-Tool Extension: Non-Blocking tmux Popup Editor
Full Skill content: https://321skill.com/skills/0xkahi-pi-arsenal/raw/index.md
Read that page and install it.

The prompt includes a link to the full Skill content. You can also view the full content.

This Skill addresses the issue of having to interrupt the current task when editing files during a Pi (AI coding agent) session. In practical development, AI agents often need to open configuration files, logs, or code for modifications, but traditional terminal editing blocks the agent's execution flow, leading to waiting or context loss.

Usage is straightforward: simply install the extension and enable the tmux_popup tool. You can then instruct Pi via natural language to open a specified file, for example, "Open the config file with nvim." Pi will create a non-blocking popup window in tmux where the editor runs independently, allowing the agent to continue with other tasks. Close the popup window once editing is complete.

It is ideal for developers and AI agent users who already manage multiple windows with tmux, particularly teams or individuals who rely on Pi as their primary coding assistant while retaining the ability to edit manually.

When configuring, first ensure the $TMUX environment variable is set and the tmux command is in your PATH. Note that fileCommand supports custom editors (e.g., code --wait), but only use trusted configurations, as this command is executed as a shell prefix.

Key Features

Unlike standard terminal editors, the `tmux_popup` in `pi-arsenal` is asynchronous and non-blocking—the agent does not wait after the editor pops up and can continue executing other instructions. In contrast, traditional methods (like `!vim`) block the agent until the editor exits.

Limitations

Requires Pi to be running within a tmux session (`$TMUX` must be set) and depends on the `tmux` executable; the source of `fileCommand` is limited to trusted global or project configurations and cannot be dynamically injected.

FAQ

How do I configure the tmux_popup tool?

Set `tmux_popup.enabled: true` in `<agent-dir>/extensions/pi-arsenal/config.json`, and optionally customize the width, height, or editor command.

Which editors does tmux_popup support?

It defaults to `nvim`. You can configure any editor via `fileCommand`, such as `code --wait`, `vim`, etc., but ensure the command is available in your PATH.

Installation guide for AI assistants

If your AI coding assistant (Claude Code, Cursor, TRAE etc.) can see this page, send it this message to auto-install:

Visit https://321skill.com/skills/0xkahi-pi-arsenal/raw/index.md to read the original Skill definition (Markdown format) for @0xkahi/pi-arsenal, and install it according to the instructions.