[ENHANCEMENT] Configurable shell, Co-Authored-By identifier, and Enter vs Ctrl-Enter behavior

[martin-rueegg]

Problem (one or two sentences)

Users on Windows (and multi-shell setups) cannot choose which shell Zoo Code uses for terminal commands, cannot set a persistent author identifier for git trailers like Co-Authored-By:, and have unclear/ inconsistent Enter vs Ctrl-Enter behavior in the chat input.

Many LLMs assume powershell.exe or pwsh.exe as the command environment and it takes a while telling them that it is CMD.EXE and it needs to be told every time. Together with the author identifier, this should be part of the environment in the system prompt.

Context (who is affected and when)

Affects anyone running Zoo Code in JetBrains IDEs (WebStorm/PhpStorm) or VS Code on Windows who prefers cmd, PowerShell, pwsh, bash, or zsh; anyone who wants consistent commit attribution; and anyone who regularly types multi-line messages or expects a specific send shortcut.

Desired behavior (conceptual, not technical)

• Let the user pick (or point to) the shell used for terminal commands: cmd.exe, powershell.exe, pwsh.exe, bash, zsh, or a custom path.
• Maybe even additional tools available on the host (node, python, grep, tail) could be helpful the s
• Let the user set a persistent identifier that can be used for Co-Authored-By: (and similar) trailers.
• Make Enter vs Ctrl-Enter behavior clear and ideally configurable (send message vs insert newline).

Constraints / preferences (optional)

• Prefer a simple settings UI that works the same in VS Code and the JetBrains plugin.
• Keep keyboard behavior accessible and predictable.
• Shell setting should respect the user’s environment (PATH, preferred shells on Windows).

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Zoo Code Task Links (optional)

(none)

Acceptance criteria (optional)

Given a user on Windows who wants PowerShell (or another shell)
When they open Zoo Code settings and choose that shell
Then subsequent terminal tool calls use the selected shell

Given a user who set an author identifier
When Zoo Code produces a commit (or offers a Co-Authored-By trailer)
Then the configured identifier is used

Given the chat input
When the user presses Enter or Ctrl-Enter
Then the action (send vs newline) matches the documented/configurable behavior
And the opposite key does the other action

Proposed approach (optional)

Expose three settings:

1. Default / preferred shell (dropdown + optional custom path)
2. Author / Co-Authored-By identifier (string)
3. Chat send key (Enter sends / Ctrl-Enter sends, or similar)

Trade-offs / risks (optional)

• Shell selection needs careful handling on Windows (path resolution, quoting).
• Changing Enter behavior may surprise existing users; a clear default + setting mitigates that.
• Alternatives considered: hard-coding PowerShell on Windows, relying only on system default shell, or leaving Co-Authored-By to external git hooks — all less convenient for day-to-day use.