Cline + Fable 5: Build or Fix Something Without Writing Code
Use a coding agent inside VS Code that builds and fixes code while you just describe what you want, powered by Fable's stamina.
Run this workflow
CI-verified, 4/4 fixtures passing.
Build this with your agent
One copy-paste hands Claude Code, Codex, or Cursor the full recipe, steps included, nothing to fetch.
Intended Use
Anyone with an idea but not the patience to write it: Cline lives in VS Code and writes, runs, and fixes files while you approve each step. CI verifies the deterministic spine: the editor settings are valid and point at the Anthropic provider with model claude-fable-5, no key. The actual building is Fable's work and is fenced.
Not for
- Letting it run fully autonomously before you trust it; keep the approve-each-change setting on
- Anyone expecting CI to verify the code it writes; that's the fenced model step
The Stack
Tested Against
cline@latestclaude-fable-5Side effects & data flow
- Network
- none, local only
- Writes
- ./cline-settings.json, ./checkcline.mjs
- Credentials
- none required
Prerequisites
- VS Code with the Cline extension
- An Anthropic API key (Claude API) for claude-fable-5
Steps
- 1
Install Cline and point it at Fable
Install the Cline extension from the VS Code Marketplace, open its settings, choose Anthropic, paste your key, and enter the model claude-fable-5. Then type something like 'build me a simple expense tracker as a web page' and approve the steps.
- 2
What CI checks: the editor settings are valid and point at Fable
CI confirms the settings parse, the API provider is anthropic, and the model id is claude-fable-5. That's the deterministic precondition, no key. The building itself is fenced.
cat > cline-settings.json <<'EOF' { "apiProvider": "anthropic", "apiModelId": "claude-fable-5" } EOF cat > checkcline.mjs <<'EOF' import { readFileSync } from 'node:fs'; const cfg = JSON.parse(readFileSync('cline-settings.json', 'utf8')); let ok = true; function check(label, cond){ console.log(label + ': ' + (cond ? 'yes' : 'NO')); if(!cond) ok=false; } check('settings parse', true); check('provider is anthropic', cfg.apiProvider === 'anthropic'); check('model is claude-fable-5', cfg.apiModelId === 'claude-fable-5'); if(!ok){ console.log('cline config check FAILED'); process.exit(1); } console.log('cline config check OK: anthropic + claude-fable-5'); EOF node checkcline.mjs - 3
Describe what you want (the model step, not checked by CI)
Tell Cline what to build and approve each change. The writing and fixing run the model, so CI never claims them. Keep the ask-before-each-change setting on until you trust it.
Eval, 4 fixtures
Last passed: verified todayprovidercontainstimeout 30s · max $0Expected:
provider is anthropic: yesmodelcontainstimeout 30s · max $0Expected:
model is claude-fable-5: yescheck-okcontainstimeout 30s · max $0Expected:
cline config check OK: anthropic + claude-fable-5clean-exitexit_codetimeout 30s · max $0Expected:
0
Results
~62,400 stars; where Fable's long-horizon stamina pays off across a chain of build steps.
Did this work for you?
Our CI checks the setup runs. You tell us if the whole thing worked. Tell us straight.
Liked this workflow?
Get new verified workflows in WebAfterAI, three issues a week (Tue, Thu, Sat).