智能工作流

Prerequisites

• tmux is installed and running.
• tmux is version 3.2 or newer if you want popup mode.
• At least one supported agent CLI is already running in a tmux pane.

1. Install Ilmari

cargo install ilmari

Verify the binary is on your PATH:

ilmari --version

Expected output:

ilmari <version>

Installation

Cargo binstall

Download the matching prebuilt release binary instead of compiling it locally:

cargo binstall ilmari

Build-time features

The default Cargo build includes the TUI and both publishing endpoints:

cargo build

You can remove features when building:

cargo build --no-default-features
cargo build --no-default-features --features tui
cargo build --no-default-features --features socket
cargo build --no-default-features --features mcp
cargo build --no-default-features --features rmcp
cargo build --no-default-features --features socket,mcp
cargo build --no-default-features --features tui,socket,mcp

Runtime flags remain parseable when an endpoint is compiled out. Enabling a compiled-out endpoint reports a status warning such as `socket support was not compiled in or MCP support was not compiled in. Builds without feature tui` run in headless mode.

`socket support was not compiled in`

Cause: the binary was built without the socket feature.

Fix:

cargo build --features socket

`MCP support was not compiled in`

Cause: the binary was built without the mcp feature.

Fix:

cargo build --features mcp

Quickstart

Configuration

No configuration file is required. When present, Ilmari reads $XDG_CONFIG_HOME/ilmari/config.toml, falling back to ~/.config/ilmari/config.toml. Malformed TOML, an unknown table/field, or an invalid typed value produces a clear startup error rather than being silently ignored.

This complete example also shows the built-in defaults:

```toml [runtime] refresh_seconds = 5 process_refresh_seconds = 15

[scanner] git = true output_tail = true

[tui] enabled = true bell = true

[palette]

Published fragment and counter reference

@ilmari_status_summary is the recommended global fragment. For a custom tmux format or menu helper, notification totals remain available as @ilmari_waiting_count and @ilmari_finished_count, while @ilmari_running_count is the live running count and @ilmari_attention_count is the combined sticky total. Ordinary counts are published separately as @ilmari_waiting_state_count, @ilmari_finished_state_count, @ilmari_terminated_count, and @ilmari_unknown_count, so no pane is counted in both attention and an ordinary state. Pane-local @ilmari_state and @ilmari_badge are available to advanced custom formats. Pane-local @ilmari_attention is 0 or 1 and carries the sticky attention latch across a popup's failed daemon snapshot followed by a direct scan; it is cleared with the other pane options when state is cleaned up or when the focused pane acknowledges attention.

Running state is live. Waiting-input and finished attention is sticky only after a qualifying transition occurs while that exact pane is not focused by any tmux client. Focusing the pane acknowledges it. An unchanged later scan does not recreate attention, but a later qualifying transition can. State for disappeared panes is removed.

Before uninstalling the TPM plugin, either set @ilmari_daemon off and reload tmux or run ilmari daemon stop from that tmux server. This stops its daemon and clears Ilmari's published fragments, counts, pane state, socket path, and MCP URL. Then remove the @plugin line and uninstall through TPM.

Troubleshooting