macOS: native boxes under Seatbelt for macOS-only work
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
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 withrunc, belowgvisorandvm. 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from public/wicket
-
Don't break the machines: node health alerts, admission control, reserved headroom, volume lifecycle, collection trackingPossibly taken @public claimed this today. Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement parked
Difficulty 5/5 Over a week Newbie friendliness 12/100
public/wicket#371 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
Windowed egress caps and standard OTLP decision records (from AgentCore, Strands Box and Dogwood)Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yantrikos/yantrik-os#1272 ·
Maintainers usually reply within 1 day
-
crate: spate-kafka priority: low tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·