Execution blocked by environment wrappers (multicall sandboxing)

Open
#830 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
macos, rust, shell

Research direction

Start by reproducing gws --help and gws auth login in the Google Antigravity agy runtime, comparing normal invocation with $(command -v gws) --help. No project file or test is named; the work would need to establish whether a supported invocation or configuration can avoid the [multicall] allowlist restriction without hardcoding an absolute path.

Written by the indexing model from the issue text.

Description

Environment Details
  • CLI Package Version: gws-cli (latest via Nix)
  • OS Platform & Version: macOS
  • Installation Method: Nix Flake
  • Runtime Environment: Google Antigravity SDK (agy runtime)
The Issue

Hey everyone,

I’m running into a weird execution blocker and was hoping to get some advice—or if this is the wrong place to ask, maybe someone could point me in the right direction.

I’m trying to automate some Workspace admin tasks by running the gws-cli within a Google Antigravity SDK sandbox environment (the agy runtime). However, whenever I try to run a standard gws command (like gws auth login or gws --help), the environment’s [multicall] wrapper intercepts and completely blocks it because it isn't in its strict allowlist.

I know this is technically an environment/sandbox restriction and probably not a direct bug in the CLI itself, but it’s completely breaking my automated workflows.

Interestingly, I did find a workaround. If I force the invocation to use the absolute binary path like this:

$(command -v gws) --help

...it bypasses the wrapper entirely and works perfectly.

What I'm looking for

Has anyone else tried using gws-cli in tightly sandboxed environments or AI agent runtimes? I’m mostly looking for advice on whether there are better ways to invoke or configure the CLI so it plays nicely with these wrappers, rather than having to hardcode the absolute path everywhere.

If this is completely out of scope here, no worries! But if anyone knows a better place to ask about Antigravity SDK environment quirks, I'd really appreciate a pointer.

Thanks in advance!

Dominant language
Rust
Stars
32.3k
Forks
2k
Avg merge
16h 3m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleworkspace/cli

All issues in googleworkspace/cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.