exec_command tool description says every command runs in a PTY
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- cli, documentation
Research direction
Start by locating the exec_command tool description and its tty parameter schema, then compare both with the documented default behavior. Update the top-level wording so it accurately describes pipe-based execution by default and PTY behavior only when tty is true; verify that the description and schema are consistent.
Written by the indexing model from the issue text.
Description
What happened?
The exec_command tool description says:
Runs a command in a PTY, returning output or a session ID for ongoing interaction.
But the same tool schema documents the tty parameter as:
True allocates a PTY for the command; false or omitted uses plain pipes.
The implementation defaults tty to false, and the process manager uses the non-PTY spawn path unless tty is true.
This makes the top-level tool description misleading: most commands do not run in a PTY unless requested.
Expected behavior
The tool description should describe the default pipe behavior and reserve PTY wording for tty: true, or otherwise match the actual default execution mode.
Additional context
I searched open issues and PRs for terms including exec_command, PTY, pipes, tty, and tool description, and did not find an existing open item that appears to cover this description mismatch.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
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 openai/codex
-
CLI enhancement model-behavior
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100