macOS: native boxes under Seatbelt for macOS-only work

Open
#49 0 comments 0 reactions 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
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
macos
Domain
security

Research direction

This is design work with no named source files, so start with the referenced research 02 section 4.6 and research 07 on nono, birdcage and agent-safehouse, then find the existing isolation tiers (runc, gvisor, vm) and the subset rule (#5) in the repo. Agree the Seatbelt profile and tier ranking with maintainers before coding. Done means an Xcode build runs in a Seatbelt box with only the workspace writable and no network except wicket's forwarders.

Written by the indexing model from the issue text.

Description

enhancement parked

Why. Some work needs macOS itself: Xcode builds, iOS simulators, Safari, Mac apps. Linux boxes can't do it, and macOS VMs are heavy: tens of GB, slow to boot, and two per Mac under Apple's licence.

What.

  • Boxes as native macOS processes under a Seatbelt (sandbox-exec) profile that starts from (deny default), as Codex and Claude Code do.
    • Files: the workspace and the system paths the tools need.
    • Network: only wicket's forwarders.
  • A separate macOS user per box, where possible.
  • Isolation tier seatbelt, ranked with runc, below gvisor and vm. Zones that require stronger isolation can't be placed there, and the subset rule (#5) applies.
  • No cgroup-style limits on macOS: document what's not enforced.
  • macOS VMs (Tart- or Lume-style) only if a real need for strongly isolated macOS work appears.

Done when. An agent builds an Xcode project in a Seatbelt box with only its workspace writable and no network besides wicket's.

Refs. research 02 §4.6, research 07 (nono, birdcage, agent-safehouse).

Dominant language
Rust
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
190

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 public/wicket

All issues in public/wicket

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.