back to home

Dicklesworthstone / agentic_coding_flywheel_setup

Bootstraps a fresh Ubuntu VPS into a complete multi-agent AI development environment in 30 minutes: coding agents, session management, safety tools, and coordination infrastructure

View on GitHub
1,315 stars
161 forks
0 issues
JavaScriptTypeScriptHTML

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing Dicklesworthstone/agentic_coding_flywheel_setup in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/Dicklesworthstone/agentic_coding_flywheel_setup)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

Agentic Coding Flywheel Setup (ACFS) 🌐 agent-flywheel.com — Interactive setup wizard for beginners > **From zero to fully-configured agentic coding VPS in 30 minutes.** > A complete bootstrapping system that transforms a fresh Ubuntu VPS into a professional AI-powered development environment. The Vision Beginner with laptop → Wizard → VPS → Agents coding for you Quick Install The installer is **idempotent**—if interrupted, simply re-run it. It will automatically resume from the last completed phase without prompts. > **Production environments:** For stable, reproducible installs, pin to a tagged release or specific commit: > > Tagged releases are tested and stable. Setting ensures all fetched scripts use the same version. --- TL;DR **ACFS** is a complete system for bootstrapping agentic coding environments: **Why you'd care:** • **Zero to Hero:** Takes complete beginners from "I have a laptop" to "I have Claude/Codex/Gemini agents writing code for me on a VPS" • **One-Liner Magic:** A single command installs 30+ tools, configures everything, and sets up three AI coding agents • **Vibe Mode:** Pre-configured for maximum velocity—passwordless sudo, dangerous agent flags enabled, optimized shell environment • **Battle-Tested Stack:** Includes the complete Dicklesworthstone stack (10 tools + utilities) for agent orchestration, coordination, and safety **What you get:** • Modern shell (zsh + oh-my-zsh + powerlevel10k) • All language runtimes (bun, uv/Python, Rust, Go) • Three AI coding agents (Claude Code, Codex CLI, Gemini CLI) • Agent coordination tools (NTM, MCP Agent Mail, SLB) • Cloud CLIs (Vault, Wrangler, Supabase, Vercel) • And 20+ more developer tools --- The ACFS Experience For Beginners ACFS includes a **step-by-step wizard website** at agent-flywheel.com that guides complete beginners through: • Installing a terminal on their local machine • Generating SSH keys (for secure access later) • Renting a VPS from providers like OVH or Contabo • Connecting via SSH with a password (initial setup) • Running the installer (which sets up key-based access) • Reconnecting securely with your SSH key • Starting to code with AI agents For Developers ACFS is a **one-liner** that transforms any fresh Ubuntu VPS into a fully-configured development environment with modern tooling and three AI coding agents ready to go. For Teams ACFS provides a **reproducible, idempotent** setup that ensures every team member's VPS environment is identical—eliminating "works on my machine" for agentic workflows. --- Architecture & Design ACFS is built around a **single source of truth**: the manifest file. Everything else—the installer scripts, doctor checks, website content—derives from this central definition. This architecture ensures consistency and makes the system easy to extend. One-Page System Data Flow Why This Architecture? **Single Source of Truth**: The manifest file ( ) defines every tool—its name, description, install commands, and verification logic. When you add or edit a tool in the manifest, the generator automatically updates the generated scripts and manifest-derived checks. The production one-liner installer ( ) is still hand-written today, so behavior changes may also require updating until full migration. **TypeScript + Zod Validation**: The manifest parser uses Zod schemas to validate the YAML at parse time. Typos, missing fields, and structural errors are caught immediately during generation—not at runtime on a user's VPS when the installer fails halfway through. **Generated Scripts**: Rather than hand-maintaining 11 category installer scripts and keeping them synchronized, the generator produces them from the manifest. This means: • A consistent, auditable view of manifest-defined install logic (some modules intentionally emit TODOs) • Consistent error handling and logging across all modules • A clear path toward future installer integration Components | Component | Path | Technology | Purpose | |-----------|------|------------|---------| | **Manifest** | | YAML | Single source of truth for all tools | | **Generator** | | TypeScript/Bun | Produces installer scripts from manifest | | **Website** | | Next.js 16 + Tailwind 4 | Step-by-step wizard for beginners | | **Installer** | | Bash | One-liner bootstrap script | | **Lib Scripts** | | Bash | Modular installer functions | | **Generated Scripts** | | Bash | Auto-generated category installers (sourced by ; execution is feature-flagged) | | **Configs** | | Shell/Tmux configs | Files deployed to | | **Onboarding** | | Bash + Markdown | Interactive tutorial system | | **Checksums** | | YAML | SHA256 hashes for upstream installers | --- The Manifest System is the **single source of truth** for all tools installed by ACFS. It defines what gets installed, how to install it, and how to verify the installation worked. Manifest Structure Each module specifies: • **description**: Human-readable name • **category**: Grouping for installer organization (base, shell, cli, lang, tools, db, cloud, agents, stack, acfs) • **install**: Commands to run (or descriptions that become TODOs) • **verify**: Commands that must succeed to confirm installation The Generator Pipeline The TypeScript generator ( ) reads the manifest and produces: • **Category Scripts** ( , , etc.) • One script per category with individual install functions • Consistent logging and error handling • Verification checks after each module • **Doctor Checks** ( ) • All verify commands extracted into a runnable health check • Tab-delimited format (to safely handle in shell commands) • Reports pass/fail/skip for each module • **Master Installer** ( ) • Sources all category scripts • Runs them in dependency order • Single entry point for running the generated installers > Note: The production one-liner installer ( ) defaults to the legacy implementations; generated installers are sourced and can be enabled per-category via feature flags during migration. To r…