rozi

Imported from tui-lipan/rozi (AGENTS.md). Install upstream with npx skills add tui-lipan/rozi. Copyright stays with the author.

Rozi agent guide

Rozi is a cross-platform, modern tiling terminal multiplexer built in Rust on tui-lipan. Its tiling layout and keyboard flow take their cues from the Hyprland window manager.

Always

• Use Cargo. The crate uses Rust 2024 and supports Rust 1.90 or newer.
• Every PTY belongs to a session server. A client that displays panes attaches to that server, but the startup launcher may remain sessionless until the user chooses or creates a session.
• Preserve unrelated worktree changes. Never discard or overwrite changes you did not create.
• Do not edit target/ or commit generated output, personal config, runtime data, logs, socket paths, credentials, or captures unless a test fixture explicitly requires scrubbed capture data.
• Tests must never write to the developer's config, state, cache, or runtime directories. An integration test that builds AppRoot calls rozi::test_support::isolate_user_dirs() first.
• Do not run Cargo commands concurrently in this workspace; they only contend on build locks.
• New OS-specific behavior belongs behind src/platform/. Existing exceptions are not precedent.
• Reusable framework behavior and framework defects belong in the sibling ../tui-lipan repository. Do not add a Rozi-local workaround; use a local path override only for iteration, then consume the released framework version.
• Keep user-facing docs in sync with behavior, CLI, configuration, and workflow changes.
• GitHub Releases is the only changelog. Do not recreate CHANGELOG.md. The /changelog command defines release-note structure; Rosie writes the prose from each PR Summary.
• Prefer a clean breaking change over aliases or compatibility shims unless the user asks for compatibility or a protocol test intentionally covers version skew.
• The repository is MPL-2.0. Contributions require a DCO sign-off.

Baseline checks

Use the narrowest useful command while editing. Before handing off a Rust application change, run:

cargo fmt --all -- --check
cargo test
cargo clippy --all-targets -- -D warnings
git diff --check

Run cargo build for broader feature work. Report any check you could not run or that failed.

Read before editing

Read the matching file before you edit in one of these areas. Each carries constraints this guide does not repeat, and violating one is usually invisible until review or CI.