Repository navigation
Research: Sandcastle as a replacement for thirdshift - #718
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 17, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a research note on whether Matt Pocock's Sandcastle could replace thirdshift, or sit under it. It uses the same criteria, in the same order, as
openhands-fit.md: subscription auth, then open source and self-hosted, then buy over build.docs/research/ ├── openhands-fit.md +├── sandcastle-fit.md # Sandcastle: subscription auth, sandboxes on this host, §1 coverage, conventions └── warp-factories-and-alternatives.mdConclusions:
claudeorcodexsession in a sandbox on a branch. It isn't a factory: it has no Claims, PR handling, Repair loop, Self-merge, Spec runs, Passes, Security work or notifications.claude -p, with aclaude setup-tokentoken inside containers. Codex uses the ChatGPT login when it runs on the host; inside a container you mount the login yourself.--dangerously-skip-permissionsby default, writes~/.gitconfigon every run, and leaves the agent running after an abort. The container mode has an open.gitescape (Worktree sandboxes mount the host .git read-write, so hooks and config written in the container run on the host mattpocock/sandcastle#1010).src/hasn't changed since v0.12.0 on 2026-06-29.Evidence
Docs only, with no code or tests. Claims cite Sandcastle's source pinned to
7a4e7f7(still the head of upstreammain),gh api,npm view, vendor docs or this repo. Anything else is tagged [unverified], [interpretation] or [needs live check]. A script confirmed every link resolves.A claim-by-claim check of §2 (subscription auth) and §3 (sandboxes) refuted nothing the verdict rests on. It found wording to tighten, which this PR doesn't include. For example, the permission flag is settled from the code, so it doesn't need a live check.
Merge Danger
Door: two-way
Blast Radius: none
Adds one Markdown file under
docs/research/. Nothing reads it at runtime.🤖 Generated with Claude Code