Home / vs / @docmd/plugin-ai
vs@DOCMD/PLUGIN-

Bonfire Terminal vs @docmd/plugin-ai

@docmd/plugin-ai is a free, open-source, on-device plugin billed per token with no key markup, letting developers add any-provider AI to the docmd documentation toolchain. Bonfire Terminal is a finished sovereign agent rather than a plugin: on-device with local Whisper, messaging bridges, and BYO-key at cost, sold as a one-time perpetual license.

Full comparison

Bonfire Terminal vs @docmd/plugin-ai: the 16-factor comparison

Rating factor@docmd/plugin-aiBonfire Terminal
CategoryOtherAI Terminal / Local Agent
PopularityNot disclosedGrowing · indie
Hosting architectureOn-Device LocalOn-Device Local
Licensing modelOpen SourceOne-Time Perpetual
Data / training policyNot disclosedFully local — nothing leaves device
Offline capabilityNoYes
Pricing tier rangeFree (OSS)One-time license
Execution unit costPay-Per-TokenUnlimited Local Compute
API-key markupNoNo — BYO key at cost
Supported LLM providersAnyOpenAI; Anthropic; Google; Local; Any
Auth / permission typesAPI KeyAPI Key; Local/None
Phone / messaging bridgesNoneTelegram; WhatsApp
Speech recognition engineNoneWhisper (local)
Local media processingNoYes
Sovereign score68 / 10093 / 100
Sovereign Software Score

The sovereignty gap

@docmd/plugin-ai68/ 100
Bonfire Terminal93/ 100+25 on sovereignty

Where @docmd/plugin-ai lands on each weighted pillar (its bar) — the red marker is Bonfire's score. Auto-derived from the 16 factors above.

Privacy & Control@docmd/plugin-ai 20 / 35
20
Bonfire 35
Cost Efficiency@docmd/plugin-ai 25 / 25
25
Bonfire 25
Technical Capabilities@docmd/plugin-ai 8 / 25
8
Bonfire 22
Vendor Risk (lower risk = higher score)@docmd/plugin-ai 15 / 15
15
Bonfire 11
Verdict

Which should you choose?

Choose @docmd/plugin-ai if…

Choose @docmd/plugin-ai if you use the docmd documentation tool and want a free open-source plugin to add AI with any provider.

Choose Bonfire Terminal if…

Choose Bonfire Terminal if you want a complete on-device agent with speech, bridges, and BYO-key at cost, beyond a docs plugin.

FAQ

Bonfire Terminal vs @docmd/plugin-ai: FAQ

Is @docmd/plugin-ai private?

Its privacy stance is unstated, but it runs on-device and calls whatever provider you choose per token, so data leaves only when a hosted model is queried. Bonfire Terminal is similarly local-first, keeping agent work on your machine except for deliberate model calls.

Is Bonfire Terminal cheaper than @docmd/plugin-ai?

@docmd/plugin-ai is free and open source with no key markup, billed only per token, so its software cost is zero. Bonfire Terminal charges a one-time license and also adds no markup, delivering a full agent rather than a documentation plugin.

Can Bonfire Terminal replace @docmd/plugin-ai?

For general AI tasks, yes; for docmd-specific documentation generation, no. @docmd/plugin-ai is scoped to the docmd toolchain, while Bonfire Terminal is a broad on-device agent. Bonfire replaces it only if you do not need docmd's docs pipeline.

What can Bonfire Terminal do that @docmd/plugin-ai can't?

Bonfire Terminal is a complete on-device agent with local Whisper speech, local media processing, Telegram and WhatsApp bridges, and multi-provider BYO-key access. @docmd/plugin-ai is a docs-toolchain plugin with no interface, speech, bridges, or offline features of its own.

How do I switch from @docmd/plugin-ai to Bonfire Terminal?

If you used @docmd/plugin-ai for AI tasks outside documentation, install Bonfire Terminal and add your provider key for on-device agent work. Keep docmd only if you still need its documentation-building features.

Does Bonfire Terminal work offline vs @docmd/plugin-ai?

@docmd/plugin-ai is on-device but calls hosted models per token, so its AI features need a connection. Bonfire Terminal runs local Whisper and media processing offline, only reaching the network when you invoke a hosted model.