Nathan Cassell

@pyxorium.com

Colorado https://atprotocol.space

I've been looking into @attie.ai and Claude and made a draft comparison this morning to help understand how they differ. Still a work in progress, but thought it might be of interest to some folks.

draft comparison chart between attie and claude, work in progress. 

Attie vs Claude: how they reach data

Both can research the open web. The real divergence is access to the Atmosphere: Attie holds a front row ticket with backstage pass, Claude listens from the parking lot.

ATTIE'S STACK | CLAUDE'S STACK

DATA ACCESS

Open web plus Atmosphere access — A queryable database (SQL over records + backlinks) indexing public ATProto records. Runs minutes-to-hours behind the live firehose.

Open web only, no network graph — No standing ATProto access to social graph, published records, or app-specific content (e.g. Bluesky/Leaflet posts, Atmo.RSVP events).

ACCOUNT REQUIREMENT

DID + PDS repo — A persistent AT Protocol identity — required to use Attie.

No account layer — No identity, no repo, no protocol membership required.

OUTPUT

Quests & Feeds — Quests (research): builds an interactive page (tabbed/sliding sections, summaries). Feeds (customizable algorithm): a protocol pointer record, Attie's backend runs the pipeline.

Chat response / generated file — One-time output per conversation — static text or a generated file, no persistent interactive UI. Nothing persists or re-runs on its own.

MODEL OPTIONS

Any Model (Claude as default) — Swappable reasoning layer — Sonnet, Opus, or bring-your-own LLM.

Claude — Fixed — this is the model, not a pluggable component.

Footer: Based on public reporting, direct inspection, and Attie's own answers to direct questions (as of Jul 2026).

Next week’s Colorado atproto meetup is gonna be fun. We'll be doing this one at a friend’s coworking space downtown called ID345. Excited to show off some new stuff I've been working on 👀

A high upper level view looking down into the ID345 presentation space