Agent generates unquoted shell command when workspace path contains spaces (breaks `git worktree add`)

[luizv]

Description

The Warp Agent generated a shell command that interpolated a filesystem path containing spaces without quoting it. The shell split the path on whitespace, which caused git worktree add to receive the wrong number of positional arguments and print its usage: help instead of creating the worktree.

The current workspace is /Users/luizv/Developer/2026-05 Site da Jô — the space in "Site da Jô" is what breaks the command.

Steps to reproduce

1. Open a workspace whose absolute path contains a space (e.g. ~/Developer/My Project).
2. Ask the Agent to create a new git worktree (any prompt that triggers it to run git worktree add).
3. Observe the command it generates.

Actual behavior

The Agent ran:

git worktree add -b turquoise-palo-verde /Users/luizv/.warp/worktrees/2026-05 Site da Jô/turquoise-palo-verde && cd /Users/luizv/.warp/worktrees/2026-05 Site da Jô/turquoise-palo-verde

The shell tokenizes /Users/luizv/.warp/worktrees/2026-05 Site da Jô/turquoise-palo-verde into 4 separate arguments. git worktree add receives too many positional args and prints its usage help. No worktree is created, but the failure mode is non-obvious because the command appears to "complete" — there is no explicit error message saying the path was misquoted.

Expected behavior

The Agent should quote (or escape) paths that may contain spaces or other shell-significant characters when composing commands. Either:

git worktree add -b turquoise-palo-verde "/Users/luizv/.warp/worktrees/2026-05 Site da Jô/turquoise-palo-verde" && cd "/Users/luizv/.warp/worktrees/2026-05 Site da Jô/turquoise-palo-verde"

or equivalent escaping. This is a general shell-safety issue — any path the Agent injects into a command string should be quoted by default, since the Agent cannot assume the user's workspace path is whitespace-free.

Environment

• Warp version: v25.1.0
• OS: macOS (Darwin 25.3.0)
• Shell: zsh

[oz-for-oss]

@luizv

Here's what I found while triaging this issue:

This looks reproducible when the generated worktree path includes a repository or workspace name with spaces. It appears related to the broader shell-escaping class tracked in #11132, but this report identifies the specific worktree command path.

Maintainer details

I concluded that generated Agent/worktree setup commands embed worktree paths without shell escaping, so repository names containing spaces break git worktree add and cd..

Triage summary

The report is a reproducible bug in the Agent/worktree tab-config path: generated worktree setup commands can embed the computed worktree directory without shell escaping, so a repository/workspace name containing spaces turns the path into multiple shell arguments.

Evidence

• The shipped default worktree config builds commands as git worktree add -b {{autogenerated_branch_name}} {{worktree_path_prefix}}{{autogenerated_branch_name}} and cd {{worktree_path_prefix}}{{autogenerated_branch_name}} in app/resources/tab_configs/default_worktree.toml:15-17.
• materialize_default_worktree_config replaces {{worktree_path_prefix}}{{autogenerated_branch_name}} with a computed path string in app/src/user_config/mod.rs:244-252, and replace_default_worktree_placeholders performs literal string replacement in app/src/user_config/mod.rs:285-304.
• generated_worktree_path_string derives data_dir()/worktrees/<repo-name>/<worktree-name> from the repository basename in app/src/tab_configs/tab_config.rs:41-58; if the repo basename contains spaces, the generated command inherits them.
• The tab-config renderer shell-quotes template parameter values, but literal/generated path text in a command is not escaped in app/src/tab_configs/tab_config.rs:214-244 and app/src/tab_configs/tab_config.rs:363-370.
• Existing tests assert the currently rendered commands without quoting the worktree path, including app/src/user_config/mod_tests.rs:82-111 and app/src/tab_configs/tab_config_tests.rs:723-777.

Likely fix area

The narrowest fix is likely in the worktree tab-config command generation/materialization path: quote or shell-escape the generated worktree path before inserting it into git worktree add and cd, while preserving unquoted values for TOML directory fields. The broader tab-config rendering behavior should also be reviewed so command templates do not mix escaped template params with unescaped generated path literals.

Duplicate check

A repository-wide open-issue scan found #11132 as a related Agent shell-escaping issue, and #11072 as a more general generated-suggestion shell-escaping issue. I did not mark this as a duplicate because the duplicate workflow requires at least two likely duplicate issues and this report identifies a distinct worktree-tab-config command path with specific files and reproduction steps.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz