git404hub

what is fable_os fr?

appleaa123/fable_os — explained in plain English

Analysis updated 2026-05-18

4ShellAudience · developerComplexity · 3/5Setup · moderate

tl;dr

A Claude Code template that runs a small automated AI team to safely triage, fix, and self-verify small maintenance chores in your project.

vibe map

mindmap
  root((fable_OS))
    What it does
      Automated chore team
      Self-verifying fixes
      Daily maintenance loop
    Tech stack
      Shell scripts
      Claude Code
      macOS
    Roles
      Triage
      Conductor
      Worker
      Verifier
    Structure
      Memory logs
      Standing goals
      Skill recipes
    Audience
      Repo maintainers
      Claude Code users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Automate small daily maintenance chores like fixing lint warnings or flaky tests in a repo.

VIBE 2

Let an AI team propose and self-verify fixes in a private copy before touching real code.

VIBE 3

Track which chore types are trustworthy enough to ship automatically over time.

what's the stack?

ShellClaude CodemacOS

how it stacks up fr

appleaa123/fable_osjayvig79/plex-preroll-automationkelseyhightower/kubestack-release
Stars444
LanguageShellShellShell
Last pushed2015-06-07
MaintenanceDormant
Setup difficultymoderatemoderatemoderate
Complexity3/52/53/5
Audiencedeveloperops devopsops devops

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Designed for macOS with BSD shell tools, requires Claude Code and a project with an existing test command.

No license information was found in the description provided.

in plain english

This project is a ready made template that turns Claude Code, an AI coding assistant, into a small automated team that quietly maintains one of your software projects for you. Once a day, or whenever you run a single command, the team looks at what has changed recently, such as new code, open issues, or failing tests, and decides whether there is one small safe task worth doing, like cleaning up a warning or fixing a flaky test. Rather than editing your real code directly, the system does the work in a private copy of your project first. It checks its own work twice, once by having another AI review it and once by actually running your project's real tests, before showing you anything. Only after a particular type of task has proven itself successful many times in a row is it allowed to be applied automatically. Until then, everything is left for you to review and approve by hand. The work is split across four roles, each handled by a different AI model chosen to balance cost against capability. One role glances at what is new and decides if anything is worth doing, another picks the single best task and writes clear instructions for it, a third performs the work, and a fourth checks the finished result against those instructions. By default the thinking roles use the Opus model, while the hands on work uses the Sonnet model, with an optional setting to use a more capable model called Fable for the thinking roles if you have access to it. To use the system, you copy a folder along with two configuration files into the top level of any project that has a test command. Inside that folder are the instructions each AI role follows, a notebook style set of files that track what happened in each run and how trustworthy each type of task has proven to be, a place to define ongoing goals that get rechecked every day so they stay fixed, and a small library of reusable task recipes the team already knows, such as fixing lint warnings or updating dependencies. The project is built with shell scripts and designed for macOS. It was adapted from an online guide describing how to build this kind of automated agent system, with the original commands rewritten to work with Claude Code and Apple's built in command line tools.

prompts (copy fr)

prompt 1
Help me copy the loop/ folder, CLAUDE.md, and Makefile from fable_OS into my project.
prompt 2
Explain the four AI roles (triage, conductor, worker, verifier) used in fable_OS.
prompt 3
Walk me through running make tick and what happens during one cycle of fable_OS.
prompt 4
Show me how to write a new goal file in loop/goals/ for fable_OS.

Frequently asked questions

what is fable_os fr?

A Claude Code template that runs a small automated AI team to safely triage, fix, and self-verify small maintenance chores in your project.

What language is fable_os written in?

Mainly Shell. The stack also includes Shell, Claude Code, macOS.

What license does fable_os use?

No license information was found in the description provided.

How hard is fable_os to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is fable_os for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.