Skip to content

Add Pi support to sandboxy #801

Description

@AntApper

Hi, I’d like to propose adding Pi as a built-in agent to the experimental sandboxy example.

I’ve been using sandboxy to run coding agents and got Pi working with the PTY support that is already in place. Pi’s interactive UI needs a real terminal; once it is launched through the existing PTY path, it works well.

The proposed change is small:

  • Add Pi’s npm package and pi launch command.
  • Persist Pi’s agent configuration from ~/.pi/agent.
  • Forward the common provider credentials.
  • Allow the provider and npm hosts through the existing proxy.
  • Avoid applying Claude’s global-agent preload to Pi, since Pi does not install that package.

This does not change the VM, networking, or sandboxing model. Pi uses the same VM isolation, host-only network, filtered proxy, and existing PTY relay as the other agents. The install uses npm’s --ignore-scripts option.

I have a small local implementation and have tested Pi interactively on macOS 26. Before opening a PR, I wanted to check whether this is a direction the maintainers would be interested in for sandboxy, or whether you would prefer agent definitions to remain user-provided.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions