anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

devcontainer_exec tool passes command as single string instead of parsing into args #4218

New Issue
Closed
opened 2026-02-16 17:43:03 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 17:43:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @athal7 on GitHub (Jan 5, 2026).

Originally assigned to: @rekram1-node on GitHub.

Problem

The devcontainer_exec tool passes the entire command string as a single executable name to the container instead of parsing it into command + arguments.

Reproduction

When using devcontainer_exec with command git status:

Command failed (exit 127):
OCI runtime exec failed: exec failed: unable to start container process: exec: "git status": executable file not found in $PATH: unknown

Even with a shell wrapper sh -c "git status":

Command failed (exit 127):  
OCI runtime exec failed: exec failed: unable to start container process: exec: "sh -c \"git status\"": executable file not found in $PATH: unknown

Root Cause

The devcontainer exec CLI expects separate positional arguments:

devcontainer exec <cmd> [args..]

But the devcontainer_exec tool appears to be passing the entire command string as a single argument to devcontainer exec.

Workaround

Use the bash tool with the devcontainer CLI directly:

devcontainer exec --workspace-folder ~/.cache/devcontainer-clones/myrepo/mybranch git status

This works correctly because bash properly parses the command into separate arguments.

Expected Behavior

The devcontainer_exec tool should either:

  1. Parse the command string into an array (split on spaces, respecting quotes)
  2. Accept the command as an array parameter
  3. Use a shell wrapper internally: sh -c "<command>"

Environment

  • OpenCode version: latest
  • devcontainer CLI: @devcontainers/cli 0.80.3
  • OS: macOS
Originally created by @athal7 on GitHub (Jan 5, 2026). Originally assigned to: @rekram1-node on GitHub. ## Problem The `devcontainer_exec` tool passes the entire command string as a single executable name to the container instead of parsing it into command + arguments. ### Reproduction When using `devcontainer_exec` with command `git status`: ``` Command failed (exit 127): OCI runtime exec failed: exec failed: unable to start container process: exec: "git status": executable file not found in $PATH: unknown ``` Even with a shell wrapper `sh -c "git status"`: ``` Command failed (exit 127): OCI runtime exec failed: exec failed: unable to start container process: exec: "sh -c \"git status\"": executable file not found in $PATH: unknown ``` ### Root Cause The `devcontainer exec` CLI expects separate positional arguments: ``` devcontainer exec <cmd> [args..] ``` But the `devcontainer_exec` tool appears to be passing the entire command string as a single argument to `devcontainer exec`. ### Workaround Use the `bash` tool with the devcontainer CLI directly: ```bash devcontainer exec --workspace-folder ~/.cache/devcontainer-clones/myrepo/mybranch git status ``` This works correctly because bash properly parses the command into separate arguments. ### Expected Behavior The `devcontainer_exec` tool should either: 1. Parse the command string into an array (split on spaces, respecting quotes) 2. Accept the command as an array parameter 3. Use a shell wrapper internally: `sh -c "<command>"` ### Environment - OpenCode version: latest - devcontainer CLI: @devcontainers/cli 0.80.3 - OS: macOS
yindo closed this issue 2026-02-16 17:43:03 -05:00
yindo commented 2026-02-16 17:43:04 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 5, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #2206: [FEATURE] add exec tool as more secure alternative to bash tool - discusses command execution and argument parsing concerns
  • #5900: Opencode doesn't work in devcontainer (M1 rosetta) - related devcontainer functionality issues
  • #4728: devcontainer: v1.0.110 failed - related devcontainer issues

The core issue here is that devcontainer_exec needs to properly parse/split the command string into separate arguments, similar to what Python's subprocess and Node.js execFile do. Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 5, 2026): This issue might be a duplicate of existing issues. Please check: - #2206: [FEATURE] add `exec` tool as more secure alternative to bash tool - discusses command execution and argument parsing concerns - #5900: Opencode doesn't work in devcontainer (M1 rosetta) - related devcontainer functionality issues - #4728: devcontainer: v1.0.110 failed - related devcontainer issues The core issue here is that `devcontainer_exec` needs to properly parse/split the command string into separate arguments, similar to what Python's subprocess and Node.js execFile do. Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:43:04 -05:00
Author
Owner
Copy Link
Copy Source

@athal7 commented on GitHub (Jan 5, 2026):

Closing - this is actually a bug in the opencode-devcontainers plugin, not OpenCode itself. The plugin's buildExecArgs function passes the command as a single string instead of splitting it into separate arguments.

The fix is in the plugin at: https://github.com/athal7/opencode-devcontainers

@athal7 commented on GitHub (Jan 5, 2026): Closing - this is actually a bug in the `opencode-devcontainers` plugin, not OpenCode itself. The plugin's `buildExecArgs` function passes the command as a single string instead of splitting it into separate arguments. The fix is in the plugin at: https://github.com/athal7/opencode-devcontainers
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4218
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?