oh-my-fable 0.1.0 → 0.1.2

package/README.md

@@ -128,8 +128,49 @@ console.log(result.ctx.plan.steps);
 npm i oh-my-fable        # zero runtime dependencies
 ```
 
-Node ≥ 18. The `AnthropicProvider` talks to the API over `fetch` — no SDK. Bring
-any model by implementing the `Provider` interface (three methods).
+Node ≥ 18. Ships with `AnthropicProvider` and `OpenAICompatProvider` (works with
+OpenAI, Ollama, LM Studio, OpenRouter, Groq… — `ollama("llama3.1")` for a local
+model with no key), both over `fetch`, no SDK. Or bring any model by implementing
+the `Provider` interface (three methods).
+
+## Or use it from the terminal
+
+Don't want to write code? It ships a CLI (zero extra deps):
+
+```bash
+npx oh-my-fable demo                       # watch crash → resume, no API key
+
+# already use Claude Code or Codex? drive it — uses that login, no separate key:
+npx oh-my-fable run "outline a talk on durable agents" --provider claude
+
+# or a LOCAL model (Ollama / LM Studio), also no key:
+npx oh-my-fable run "outline a talk on durable agents" --provider ollama --model llama3.1
+
+# or any hosted model:
+export ANTHROPIC_API_KEY=sk-...
+npx oh-my-fable run "summarize README.md into SUMMARY.md" --tools fs
+
+npx oh-my-fable list                       # your saved runs
+npx oh-my-fable resume run_abc123          # continue one from its checkpoint
+```
+
+**You don't need an Anthropic API key.** Pick how it talks to a model:
+
+| `--provider` | uses | key? |
+| --- | --- | --- |
+| `claude` / `codex` | your Claude Code / Codex CLI login | **none** — rides the CLI's auth |
+| `ollama` | a local Ollama model | **none** |
+| `--base-url <url>` | LM Studio / OpenRouter / Groq / any OpenAI-compatible | per that server |
+| `openai` | OpenAI | `OPENAI_API_KEY` |
+| *(default)* | Anthropic | `ANTHROPIC_API_KEY` |
+
+(The CLI-driven providers are text-only — great for planning/reasoning runs; they
+don't expose `--tools`.)
+
+You watch the plan form and each step get reflected on, live. `--tools fs` gives
+the agent a sandboxed `read_file`/`write_file`/`list_dir` (confined to the working
+directory) so a terminal run can actually produce files; without it, runs are
+pure-reasoning. Every run is checkpointed, so `resume <runId>` always works.
 
 ## Tools