DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run FuXi with bypassed approvals inside a container with Fuxi

Let FuXi run tool calls without prompts, but only inside a disposable container or VM.

Authorization notice. Fuxi is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Remote script. The install step pipes a remote bootstrap script into bash, so review it before running it inside your sandbox.

Who it is forA developer doing a large automated refactor who wants fewer approval prompts and has an isolated environment to run it in.

The problemApproving every tool call slows long refactors, but unrestricted execution on a main workstation is risky.

The outcomeFuXi runs its tool calls without prompts inside an isolated environment, and the host machine stays protected.

What you need first

  • A FuXi account (`fuxi login`) or your own LLM provider API key
  • A macOS, Linux, or Windows terminal
  • A local code repository to work in

Steps

  1. Start a disposable container or VM and open a shell inside it. (inferred, check the README)
  2. curl -fsSL https://downloads.fuxicode.com/bootstrap.sh | bash
  3. fuxi --dangerously-skip-permissions (inferred, check the README)
  4. Type your refactor prompt and review the changes when the session ends.
  5. Remove the container or VM when the work is done.

Prompt for your agent

Inside a disposable container or VM, install FuXi from fuxicodex/Fuxi and start it with `fuxi --dangerously-skip-permissions` in the repository at <repo-path>. Expected output: the session starts in bypassPermissions mode and completes the requested change. Verify by checking the diff in the repository and confirming nothing outside the sandbox changed.

Caveat. The README says root and sudo are rejected on Linux and macOS, and that this flag should be used only in a container or VM, so do not run it on your main workstation.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page