Skip to main content
AIDiveForge AIDiveForge

AI Secretary vs Alchimist

AI Secretary and Alchimist are both personal assistants tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

AI Secretary

AI Secretary

Telegram AI Secretary is a self-hosted Python daemon that listens to a Telegram account via Telethon, runs each incoming message through configurable notification rules and an LLM filter, then fires only the alerts that pass to your phone through ntfy. Setup requires a working Python environment, Telegram API credentials, an LLM endpoint, and an ntfy instance — none of which come pre-configured. The filtering logic lives in notification_rules.py, which you edit directly; there is no UI. It handles muted groups, direct urgency signals, and same-day scheduling well. It does not handle anything beyond single-message evaluation — no thread awareness, no conversation memory across sessions.

Alchimist

Alchimist

The extension parses the active web page and feeds that content as grounded context into your chosen persona, then generates output without sending anything to a hosted backend — your API key, your browser, your data. Persona-based rewriting lets you reshape or refine page content through a defined voice, which matters when you're producing client work that needs to sound like someone specific. The client-side architecture is the core differentiator: nothing leaves the browser except the call you make to your own API endpoint. That same architecture is the ceiling — there is no shared workspace, no team queue, and no way to chain steps across sessions without starting over.

AttributeAI SecretaryAlchimist
PricingFreeFree
Free trialNoNo
Open sourceYesYes
Has APINoNo
Self-hosted optionYesYes
PlatformsPythonBrowser (Chrome extension)
Pros
  • LLM-assisted urgency evaluation catches natural-language signals like 'I'm outside' or 'free tonight?' that keyword rules miss, so messages requiring a real response get through even when Telegram is fully muted.
  • Fully self-hosted with no external service dependency beyond your chosen LLM endpoint, which means your message content never touches a third-party notification broker.
  • Editing notification_rules.py gives you direct control over filter logic without an abstraction layer between your intent and execution, so rule changes take effect on the next restart without waiting on a vendor's UI.
  • ntfy as the delivery target works on Android and iOS without a proprietary app, so you receive filtered alerts on standard push infrastructure you likely already run.
  • MIT license with a systemd unit file included, so deploying this as a persistent background service on a Linux machine is a copy-paste operation rather than a packaging project.
  • Full client-side execution with BYOK, so no content ever reaches a vendor-controlled server — which means teams handling confidential client copy or sensitive research data get a hard architectural guarantee, not a privacy policy promise.
  • Page content is parsed and used as the grounded context for every generation cycle, so output is anchored to what you are actually reading rather than what you remembered to paste — which eliminates the copy-paste-and-hope workflow that produces off-target drafts.
  • Persona configuration shapes output voice consistently across rewriting and refinement passes, so ghostwriters producing work for a specific client voice do not have to re-specify tone on every prompt.
  • Multi-stage interaction with page arguments is described in the repo, so a researcher can push back on a source's claims across several passes without leaving the extension or manually re-feeding context each time.
Cons
  • Each message is evaluated in isolation with no conversation memory across sessions, so follow-up messages that only make sense in context — 'still waiting', 'did you see my last message' — can fail the urgency filter even when the original message would have passed; teams who need thread-aware filtering have to maintain their own context-injection layer or abandon this tool for a hosted alternative.
  • All configuration changes require editing Python source files directly and restarting the process; there is no API, no web UI, and no hot-reload, which means non-technical household members or teammates cannot adjust their own notification rules without developer involvement.
  • The tool listens to a single Telegram account only — no multi-account support, no other messaging platforms — so anyone filtering across Signal, WhatsApp, or multiple Telegram accounts simultaneously has to run and maintain separate instances or switch to a unified notification management service.
  • There is no collaboration layer or shared workspace. The moment a second person needs to review, edit, or continue a session, they are starting from scratch — teams doing any kind of coordinated content production will immediately hit this wall and route around it by exporting output manually, which is a workflow, not a feature.
  • Session state does not persist across browser sessions. Any multi-stage work in progress is lost when the tab closes or the browser restarts, which means long research threads or iterative drafting projects require manual continuity management by the user.
  • The license is custom and restrictive per curation review — teams intending to fork the extension, embed it in a product, or redistribute a modified version face legal ambiguity that a standard MIT or Apache-licensed tool would not create. When that matters, teams switch to an extension built on a clearly permissive license.
  • There is no API surface and no integration hooks. Output cannot be pushed to a CMS, a project management tool, or any downstream system without manual copy-paste — at the point where a team needs even basic automation around the output, this tool is not part of the answer.
Bottom line

AI Secretary and Alchimist are closely matched on pricing model, openness, and API availability — pick by feature set and platform support in the table above.

Frequently asked questions

What is the difference between AI Secretary and Alchimist?

AI Secretary is Free and open source, while Alchimist is Free and open source. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is AI Secretary better than Alchimist?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.

AI Secretary vs Alchimist: which should I pick?

Pick AI Secretary if its pricing model, openness, or platform fit matches your constraints; pick Alchimist otherwise. Check free-trial availability on each listing if you want to test before committing.

Comparison data is sourced and verified by the AIDiveForge data pipeline. AIDiveForge is editorially independent.