[Agentic DX] tmuxp: low-to-high lift machine-output and command-contract roadmap
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the command modules under src/tmuxp/cli/*, the output helpers, and the current JSON support scope. This issue is a broad roadmap rather than a scoped change, so first identify one command family and define its output, schema, exit-code, and plan-mode contract. Done means the selected scope has consistent machine-readable behavior and regression coverage.
Written by the indexing model from the issue text.
Description
Context
Review focused on src/tmuxp/cli/* command modules, output helpers, and current JSON support scope.
Goal
Make tmuxp command behavior consistently machine-readable while keeping strong human UX.
Low-lift ideas
- Standardize
--json/--ndjsonsupport and semantics across all user-facing subcommands. - Publish output schema examples (and schema version field) for machine-output commands.
- Document exit code contracts per command family.
Medium-lift ideas
- Ensure all commands route output through shared output abstractions for parity.
- Add
--dry-run --jsonfor side-effectful commands (load,import,convert, etc.). - Add regression tests for output contract stability.
High-lift ideas
- Add plan/execution graph output for automation orchestrators.
- Expose machine-readable command metadata (args, side effects, output modes).
Done when
- Output contract is consistent across subcommands.
- Side-effectful operations have inspectable plan mode.
- Tooling integration requires less command-specific handling.
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 248
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tmux-python/tmuxp
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
tmux-python/tmuxp#1026 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
tmux-python/tmuxp#939 · 1 comment ·
-
enhancement WorkspaceBuilder
Difficulty 4/5 3-5 days Newbie friendliness 48/100
tmux-python/tmuxp#1062 ·
-
enhancement need-comments WorkspaceBuilder
Difficulty 5/5 Over a week Newbie friendliness 35/100
tmux-python/tmuxp#1058 · 2 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
tmux-python/tmuxp#1053 · 10 comments ·
All issues in tmux-python/tmuxp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100