possibilities

Let zmx own fmx's PTYs: a direct-client design sketch

This is a concrete use case for libzmx discussion #127. It is a design sketch, not a request that zmx adopt every name or command shown here. We are happy to reshape it around zmx's preferred architecture and contribute the work incrementally.

What we are building

fmx is an OpenTUI interface for fx. It runs several fx processes and renders each terminal with OpenTUI's libghostty-backed terminal widget. In fmx terminology, one fx process plus its embedded terminal is an Instance.

Today fmx creates and owns a PTY for every Instance:

possibilities

Seed epic — fn-7-gist-demo

• Tasks: 1

Contents

1. Epic spec

Tasks

possibilities

Seed epic — fn-7-gist-demo

• Tasks: 1

Contents

1. Epic spec

Tasks

possibilities

Tmux Features in ArtHack

1. tmuxctl CLI

The tmuxctl application provides fast tmux control optimized for agent workflows. Located in /Users/mike/code/arthack/apps/tmuxctl/.

Subcommands (16 total, defined via run_*.py modules):

Subcommand	Purpose

possibilities

Tmux Features Inventory - arthack repo

Date: April 12, 2026
Status: Post-removal of hooks-level tmux integration
Repo: /Users/mike/code/arthack

---

Executive Summary

The arthack project maintains a lightweight, agent-friendly tmux integration layer. The tmux hooks-tracker capture (which was removed on April 12, 2026) has been fully deprecated. The current state consists of:

possibilities

hookctl pipe events — consumer guide

A guide for app developers who want to build realtime UIs on top of hookctl's mutation stream. Covers both surfaces exposed by the pipeline: the raw per-mutation event stream and the reduced hook_jobs state slice. Pick whichever matches the shape your app actually needs — sometimes it's both.

The big picture

possibilities

Join — Phone Screen Quick Reference

Company	Join (join.build)
Role	Staff Software Engineer (Web)
Interviewer	Jon (jon@join.build), likely engineering leadership
Platform	Zoom (booked via calendar link)
Format	Phone screen, not a coding interview
Team size	Small engineering team, cross-functional pods (devs, designer, PM, EM)

possibilities

#!/usr/bin/env python3
"""E2E test driver for the prise plug system.

Connects to a running prise server and exercises:
1. spawn_plug — spawn the echo plug
2. list_plugs — verify it appears
3. call_plug — round-trip RPC echo
4. notify_plug — fire-and-forget to plug
5. Restart — kill plug, verify it restarts
6. Timeout — spawn a non-responding plug, verify timeout

possibilities

#!/usr/bin/env python3
# /// script
# dependencies = ["msgpack"]
# ///
"""Echo plug for prise E2E testing.

Registers as a plug, echoes back any call_plug requests,
and sends periodic heartbeat notifications.
"""
import os

possibilities

Prise Plug System — Developer Guide

Extracted from the prise(5) manual page. This documents the plug protocol, Lua API, CLI, and includes complete working examples.

PLUG SYSTEM

Plugs are external processes that extend prise with capabilities that would block the single-threaded UI event loop — file watching, database queries, network listeners, etc. Plugs communicate with the server via msgpack-RPC over the same Unix socket used by TUI clients.