Thanks for helping make executainer better.
- Read the README and INSTALL flow first.
- Keep changes narrow. This repo is intentionally small.
- Prefer explicit behavior over clever abstractions.
- If the change affects operator trust, docs are part of the change.
Prerequisites:
- Rust toolchain
tmux- Codex CLI available as
codex
Run the core checks before you push:
cargo fmt --check
cargo clippy --all-targets --all-features -- -D warnings
cargo testIf you are changing onboarding or release docs, also walk through:
cargo run -- --help
cargo run -- doctor --jsondoctor validates your local machine, so it is expected to fail if tmux or codex is missing.
- Explain the user-facing problem first.
- Include verification commands and results.
- Call out docs changes when behavior changes.
- Keep follow-up work out of scope unless it is in the direct blast radius.
This project wins by staying legible.
- Small CLI surface
- Deterministic artifacts
- Thin orchestrator
- Clear failure states
If a change makes the tool feel smarter but less inspectable, that is usually a bad trade.