OmO fixes tmux paths that could run model-written commands
The 5.1.34 source tag includes fixes for task descriptions, pane titles and worktree paths reaching shell or tmux expansion. Package-index availability for this version was not confirmed during review.
OmO’s new 5.1.34 source tag closes a route from model-written display text to command execution in its tmux integration. The maintainers describe fixes for subagent task descriptions and team worktree paths that were being interpreted rather than kept literal.
The concrete problem sits outside the agent’s ordinary decision to run a shell tool. A task description intended for a placeholder banner could pass through two shell interpretation levels, while the old escaping handled only one. Shell substitutions and variables inside that description could therefore be evaluated in the user’s pane, according to the merged fix.
Two interpretation layers, two fixes
Pull request 10231, merged October 15 at 21:28:51 UTC, applies the existing nested-command quoting helper to both banner arguments. The tagged implementation also removes NUL bytes, bounds the displayed description to 2,000 characters and escapes tmux format markers in the shortened pane title.
The author reports real-shell canary tests that failed before the change and passed afterward, along with real-tmux title checks. AITrending inspected the English explanation and the fixed source; it did not independently run those tests.
A follow-up, 10235, merged at 21:58:37 UTC, addresses team-mode working directories. The model can supply a member’s worktree path through team_create. Passing that path directly to tmux’s pane-splitting directory option allowed tmux format expansion; some format syntax can invoke shell commands. The fix doubles format-marker characters at both split sites so the directory is treated literally.
These are distinct parser boundaries: shell quoting protects the banner, while tmux format escaping protects titles and directories. Passing a value as a command argument alone did not remove the second interpretation step.
Check the edition and the delivered version
The repository ships a standalone OmO Native application on its senpi engine, an OpenCode Ultimate plugin and a Codex Light edition. The reviewed team-layout code attaches to OpenCode sessions; the finding concerns the affected tmux paths, not a demonstrated issue in every edition or on every operating system.
The English installation guide distinguishes omo-ai for standalone use, the oh-my-openagent OpenCode installer and the lazycodex-ai Light installer. Model-provider credentials and usage costs remain separate from those packages. The project uses a Sustainable Use License with internal-business and non-commercial restrictions rather than an unrestricted permissive license.
At review, version-specific npm lookups for those three package names at 5.1.34 returned 404. The source tag and its fixes are inspectable, but AITrending cannot confirm that a normal package update already delivers this version. Users of affected tmux workflows should check the version their installation actually receives against the tagged fixes.
The reviewed sources do not establish exploitation in real deployments or a complete affected-version range. The news is the disclosed command-expansion mechanism and its source fixes, not evidence of a wider breach.
