Document/support Oh My Pi (omp) in Terminal Threads

[riccardo-algorime]

What are you proposing?

Please add/document first-class Terminal Threads support for Oh My Pi (omp) as a terminal-backed agent CLI.

This is specifically about Zed Terminal Threads, not ACP/external-agent integration. omp is designed as a terminal-first coding agent, and Zed's Terminal Threads are the right place to run it while keeping it visible in the Threads Sidebar.

A first useful version could be documentation-only if Zed already has the needed terminal primitives:

• mention omp alongside Claude Code, Codex, Amp, OpenCode, and Pi as a terminal-agent CLI users can run in Terminal Threads;
• provide the recommended omp notification setup for Zed terminal threads, equivalent to the current Pi / Claude Code / Amp / OpenCode notification recipes;
• document whether OMP can update the terminal title/status in a way Zed uses in the Threads Sidebar;
• if OMP needs an extension or hook, show the correct .omp path and package/API import for current OMP, rather than the older Pi .pi example.

Why does this matter?

Terminal Threads are useful because they preserve the native terminal UI of agent CLIs while still giving Zed a thread/sidebar workflow. OMP is explicitly terminal-first, so users should be able to run it in a Zed Terminal Thread and still get the important Zed-side UX:

• know which thread needs attention;
• get a notification when OMP finishes a turn or asks for permission/input;
• see useful terminal-thread titles/status in the sidebar;
• avoid confusing OMP with older Pi config paths or ACP-only setup.

Right now the docs include a Pi notification recipe using .pi/extensions/zed-bell.ts and @earendil-works/pi-coding-agent, but Oh My Pi uses the omp CLI, @oh-my-pi/pi-coding-agent, and .omp conventions. Users coming from OMP may not know whether the Pi recipe applies, whether it needs translation, or whether Zed supports OMP-specific terminal signals already.

Existing related discussions I found

I did not find an existing OMP / Oh My Pi specific Terminal Threads discussion.

Related generic Terminal Threads threads:

• First Class Terminal Agent Support for Parallel Agents Feature #55458 — first-class terminal-agent support shipped as Terminal Threads
• Default command to run for new terminal threads #57427 — default command / terminal-agent profiles for new terminal threads
• Making terminal threads persistent / adding support for resurrection #57428 — persistence/resume for terminal-agent sessions
• Have Terminal Threads display a balloon popup when waiting for user input or agent has responded as done in ACP #58243 — popup notifications for terminal threads waiting for input or completion
• "Add to Agent Thread" not working with Terminal Threads #57304 / Send selection as context to terminal threads #58131 / Editor Selection as Context to terminal threads #57476 — sending editor selection/context to terminal threads

Those cover the general Terminal Threads direction. This request is narrower: make the OMP terminal-thread path clear and supported/documented.

Possible acceptance criteria

• Zed docs have an Oh My Pi / OMP section under Terminal Threads.
• The section shows how to launch omp in a Terminal Thread.
• The section shows the correct OMP notification hook/extension for terminal bell notifications, or states that OMP supports this out of the box if that is true.
• If Zed uses terminal title updates for sidebar context, the docs state whether OMP supports this and how to enable it.
• If future terminal-agent profiles/default commands are added, OMP can be represented as a profile using omp as the command.

Non-goals

• Not asking for ACP support here.
• Not asking Zed to implement OMP itself.
• Not asking for a special native integration if a documented terminal-hook path is enough.

Context

Oh My Pi repo: https://github.com/can1357/oh-my-pi
Zed Terminal Threads docs: https://zed.dev/docs/ai/agent-panel#terminal-threads

[upwindchange]

I land here exactly because I want to try to run omp in terminal thread instead of ACP. There is no documentation anywhere on how to achieve this.