Bonfire Terminal vs @morphy-agent/cli
@morphy-agent/cli is an on-device coding assistant run from the command line and keyed by API. Bonfire Terminal shares its local footing but broadens the scope: a full agent and terminal with Telegram and WhatsApp bridges, local Whisper, and any provider billed at cost with no markup under one perpetual license.
Bonfire Terminal vs @morphy-agent/cli: the 16-factor comparison
| Rating factor | @morphy-agent/cli | Bonfire Terminal |
|---|---|---|
| Category | AI Coding Assistant | AI Terminal / Local Agent |
| Popularity | Not disclosed | Growing · indie |
| Hosting architecture | On-Device Local | On-Device Local |
| Licensing model | Not disclosed | One-Time Perpetual |
| Data / training policy | Not disclosed | Fully local — nothing leaves device |
| Offline capability | Not disclosed | Yes |
| Pricing tier range | Not disclosed | One-time license |
| Execution unit cost | Not disclosed | Unlimited Local Compute |
| API-key markup | Not disclosed | No — BYO key at cost |
| Supported LLM providers | Not disclosed | 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 | 39 / 100 | 93 / 100 |
The sovereignty gap
Where @morphy-agent/cli 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 @morphy-agent/cli if…
Choose @morphy-agent/cli if you want a focused on-device coding CLI and are happy configuring it with an API key.
Choose Bonfire Terminal if…
Choose Bonfire Terminal if you want a broader on-device agent with messaging bridges, local Whisper, and media processing.
Bonfire Terminal vs @morphy-agent/cli: FAQ
Is @morphy-agent/cli private?
@morphy-agent/cli runs on-device, giving it a solid local privacy posture, though it does not publish a training-data policy. Bonfire Terminal is also local-first, keeping your code and prompts on your machine rather than sending them to a vendor cloud.
Is Bonfire Terminal cheaper than @morphy-agent/cli?
@morphy-agent/cli does not list public pricing. Bonfire Terminal is a one-time perpetual license plus your own LLM usage at cost with no markup, so after purchase you pay only metered tokens rather than any recurring assistant fee.
Can Bonfire Terminal replace @morphy-agent/cli?
Yes, for coding-assistant work. Bonfire Terminal runs on-device and handles agentic tasks with any provider. @morphy-agent/cli is a focused coding CLI, so Bonfire covers that role while adding bridges, transcription, and media handling.
What can Bonfire Terminal do that @morphy-agent/cli can't?
Bonfire Terminal adds Telegram and WhatsApp bridges, local Whisper transcription, and local media processing on top of on-device agent work. @morphy-agent/cli is a coding CLI without messaging bridges, speech recognition, or media processing built in.
How do I switch from @morphy-agent/cli to Bonfire Terminal?
Install Bonfire Terminal and reuse your existing provider key. Both run on-device, so your code never leaves your machine during the switch, and you gain bridges, local Whisper, and media processing beyond a command-line coding tool.
Does Bonfire Terminal work offline vs @morphy-agent/cli?
@morphy-agent/cli runs on-device, so it can operate locally, though its offline behavior is not documented. Bonfire Terminal runs on-device with local models and Whisper, so its core features work without a connection just as reliably.