Bonfire Terminal vs @effect/ai-openai
@effect/ai-openai is a free, open-source TypeScript library that runs on-device, collects no data, and connects to OpenAI with pay-per-token billing. Bonfire Terminal shares the BYO-key, no-markup approach but delivers a finished sovereign agent: a one-time license, local Whisper speech, local media processing, and Telegram and WhatsApp bridges, all on-device.
Bonfire Terminal vs @effect/ai-openai: the 16-factor comparison
| Rating factor | @effect/ai-openai | Bonfire Terminal |
|---|---|---|
| Category | AI Agent Framework | AI Terminal / Local Agent |
| Popularity | GitHub 15.3k stars | Growing · indie |
| Hosting architecture | On-Device Local | On-Device Local |
| Licensing model | Open Source | One-Time Perpetual |
| Data / training policy | Library no data collection | Fully local — nothing leaves device |
| Offline capability | No | Yes |
| Pricing tier range | Free (OSS) | One-time license |
| Execution unit cost | Pay-Per-Token | Unlimited Local Compute |
| API-key markup | No | No — BYO key at cost |
| Supported LLM providers | OpenAI | OpenAI; Anthropic; Google; Local; Any |
| Auth / permission types | API Key | API Key; Local/None |
| Phone / messaging bridges | None | Telegram; WhatsApp |
| Speech recognition engine | None | Whisper (local) |
| Local media processing | No | Yes |
| Sovereign score | 69 / 100 | 93 / 100 |
The sovereignty gap
Where @effect/ai-openai lands on each weighted pillar (its bar) — the red marker is Bonfire's score. Auto-derived from the 16 factors above.
Which should you choose?
Choose @effect/ai-openai if…
Choose @effect/ai-openai if you are building TypeScript applications with the Effect ecosystem and want a typed, composable OpenAI integration library.
Choose Bonfire Terminal if…
Choose Bonfire Terminal if you want a ready on-device assistant with voice, media, and messaging rather than a code library to build with.
Bonfire Terminal vs @effect/ai-openai: FAQ
Is @effect/ai-openai private?
As a library, @effect/ai-openai collects no data itself and runs in your process, though prompts still go to OpenAI. Bonfire Terminal is local-first, keeping data on the device and never training on it, and it manages that privacy for you rather than depending on how you code.
Is Bonfire Terminal cheaper than @effect/ai-openai?
The library is free and open-source with only pay-per-token OpenAI costs. Bonfire Terminal is a one-time perpetual license, yet both bill model usage at provider cost with no markup, so token spending is identical once you own Bonfire.
Can Bonfire Terminal replace @effect/ai-openai?
For end users, yes; for developers building Effect apps, no. The library is a building block for TypeScript software, while Bonfire Terminal is a packaged assistant. If you want to use AI rather than integrate it in code, Bonfire fits.
What can Bonfire Terminal do that @effect/ai-openai can't?
Bonfire Terminal ships local Whisper speech, local media processing, and Telegram and WhatsApp bridges as working features. @effect/ai-openai is a single-provider library with no voice, media, or messaging, and it only targets OpenAI.
How do I switch from @effect/ai-openai to Bonfire Terminal?
If you used the library to build a personal tool, install Bonfire Terminal instead and add your own key at cost. You gain voice, media, and messaging without writing code. Keep the library for embedding OpenAI into custom TypeScript applications.
Does Bonfire Terminal work offline vs @effect/ai-openai?
@effect/ai-openai has no offline capability since it targets OpenAI's hosted API. Bonfire Terminal runs its agent, local Whisper, and media processing on-device, so much of it works offline, needing the network only when your chosen cloud LLM is called.