Secure and Isolated Multi-Agent Claude Code Development Seat on FreeBSD

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: advanced
Categories: Quality Control, Context & Memory, CLAUDE.md, Subagents, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Securely and systematically developing code using Claude Code agents in an isolated environment, mitigating risks associated with 'dangerously mode' and ensuring code quality through a structured review process.

Summary

A detailed setup for a secure, isolated development environment ('Dev Seat Jail') on FreeBSD, leveraging a multi-agent Claude Code configuration (Fable orchestrator, Haiku explorer, Sonnet implementer, Opus reviewer) in 'dangerously mode.' The workflow includes strict network isolation, self-hosted source control with merge request gates, and integration of a CLAUDE.md file for consistent guidance.

Why it is useful

This workflow provides a robust and detailed solution for securely leveraging Claude Code agents, particularly in 'dangerously mode,' by implementing strong isolation and a structured multi-agent review process. It addresses critical security concerns while enabling powerful AI-driven development, making it highly valuable for advanced users seeking to integrate AI into their secure development pipelines.

Workflow

1. Set up a FreeBSD jail with linuxulator for the Dev Seat.
2. Install headless VSCode with the Claude extension inside the jail.
3. Configure VSCode remote SSH access from a local laptop to the headless VSCode.
4. Set up a self-hosted source control system (e.g., Forgejo) outside the Dev Seat jail.
5. Grant the Dev Seat jail access to a forked repository for development, requiring merge requests for main branch integration.
6. Implement LAN isolation for the Dev Seat jail using a firewall (pf).
7. Implement WAN isolation for the Dev Seat jail using an HTTP proxy whitelist for necessary sites (Anthropic, OS/coding sites).
8. Configure Claude to run in 'dangerously mode' within the isolated environment.
9. Assign specific roles to Claude agents: Fable as orchestrator, Haiku as explorer, Sonnet as implementer, and Opus as reviewer.
10. Gate 1: Plan with Fable until a development plan is signed off by the user.
11. Fable orchestrates the execution of build, test, and review steps.
12. Gate 2: Fable issues a merge request (MR) in source control for the user's final code review.

Tools / artifacts

• FreeBSD jail
• linuxulator
• Headless VSCode
• Claude extension (VSCode)
• VSCode remote SSH
• Forgejo (or similar self-hosted source control)
• Firewall (pf)
• HTTP proxy whitelist
• Fable (Claude agent)
• Haiku (Claude agent)
• Sonnet (Claude agent)
• Opus (Claude agent)

Validation signals

• User states 'I had Claude help me set up a whole development seat' indicating successful implementation.
• User has copied a 'CLAUDE.md file into the seat as it has hard some won wisdom and my coding philosophy,' implying practical use and refinement.
• User is 'planning to build a software defined network test platform using FreeBSD jails' for better isolation, indicating ongoing commitment and improvement.
• The workflow includes structured 'Gate 1' and 'Gate 2' for planning and code review, demonstrating a quality control process.

Cautions

• Running Claude in 'dangerously mode' requires extreme caution and robust isolation, which this workflow attempts to provide.
• Improper firewall or proxy configuration could lead to significant security vulnerabilities.
• The user is ultimately responsible for thoroughly reviewing all code generated by the AI before merging into production.

Limitations

• Requires advanced system administration knowledge (FreeBSD jails, firewalls, networking).
• Specific to FreeBSD, though the underlying concepts are transferable.
• Limited community validation at this stage.
• The 'dangerously mode' aspect, while mitigated, still carries inherent risks if isolation measures fail.
• The specific content of the 'CLAUDE.md' file is not provided, only its existence is mentioned.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.