Claude Duet review vs Allternit
Answer me with artifact · 2026-10-24 12:55

New version 0.5.7

You have 0.5.5. Found when this page was made.

What's new:

Run in a terminal:

npx skills update answer-me-with-html -y

Or tell your agent:

Update answer-me-with-html
See what's new

Claude Duet review vs Allternit

Each point in the review, checked against Allternit main on 2026-10-24

Allternit already has most of what the review praises. It also has all four of the things the reviewer was missing. Four things are not built: a separate bots app with its own settings, Quiet Hours, location, and Write in my style.

A0

Merged and live on the web, 2026-10-24

Bots app and Quiet Hours are merged

ai #810 and platform #1842 are merged. ai.allternit.com/bots is live, the Quiet Hours API is live, and the docs guide is live. Migration 102 was applied by hand. The docs CI was failing because of another page; #1844 fixed it.

Surface State
ai.allternit.com/bots (Desktop + phone layout) live
Quiet Hours API + database live
docs.allternit.com/guides/allternit-bots-app live
m.allternit.com/bots (PWA install as "Allternit Bots") needs deploy go
Allternit Desktop (runtime + own Bots window) needs publish + app build go
bots.allternit.com needs domain + Clerk go
What should go out next?
A

Where we stand

Mostly aligned

We match or beat Duet on 8 of the 13 points. The review's four complaints are things we already ship. The biggest gap is that Duet is its own product, and our bots are a mode inside the full app.

B

Things the reviewer likes

Duet Allternit today Status
Own mobile app, own settings Bots live inside the full app. Each bot can go on the Home Screen (m.allternit.com/b/<id>), but it opens the full app, and settings are the shared Settings
Own place on the web (claude.ai/messages) No bots-only URL. Bot Mode is a mode inside ai.allternit.com
Tasks view, proactive suggestions Chat · Threads · Tasks · Bot deck, Up next, bot-suggested tasks (suggest_task, Go ahead / Not now)
Cards that don't block each other Question card, decision trees, approval + suggestion cards act one at a time check email-draft cards live
Quiet Hours Per-thread All / Mentions / Muted only. The quiet-hours policy is in Factory attention, but users can't set it
Location sharing Nothing
Write in my style Personality is per bot. Nothing learns how you write
Opus 5.5 In gizzi provider catalog, any brain per bot
Picks up Claude memories Settings → Memory → Import (Claude export prompt) + Memory Drive import
Main chat + channels Main chat + threads + projects + unified channel API (Telegram, Slack, email, …)
C

The reviewer's complaints — already ours

Duet miss Allternit
Can't rename / personalize Edit bot: Name, Purpose, avatar packs, colour, voice
Can't import from other assistants Memory Drive import: Claude, ChatGPT, Gemini, other (dry-run, filters secrets)
Can't see its memories Settings → Memory list + bot → Memory tab + Memory Drive files (edit, history)
No scheduled-tasks or usage view Automation Tasks calendar/graph (All bots) + Settings → Usage by brain/bot

These four belong on the www Bots page and in the next film, as a direct "what Duet doesn't do" list.

D

What to build to close the gaps

  1. Allternit Bots, its own app: the same allternit-ai build, with a bots-only mode, like office.allternit.com. It opens straight into your main bot's chat. Its own rail shows bots, channels and tasks. Its own Settings has Notifications and Quiet Hours, Location, Writing style, Memory, Routines, Usage and Channels. It installs as its own PWA with its own icon and name. Desktop gets it as a window, and the full app keeps Bot Mode as today.
  2. Quiet Hours: Settings → Notifications gets a start time, end time and time zone. The server holds pushes and bot pings, then sends one summary when quiet hours end. It re-uses the QuietHours policy from Factory attention.
  3. Location (opt-in): the phone and PWA share a rough location ("near X") with the bot. A chip shows when it is on. It is off by default, the opposite of Duet, on purpose.
  4. Write in my style: the bot learns your style from mail and messages you sent. It keeps it in a Memory Drive file, style.md, that you can read and edit. Drafts use it, with one toggle, on by default.

All three ship on Desktop, phone layout, and PWA, with docs, in one PR each.

Where should the bots app live?
Which gaps should I build?