Cryptograss:Magenta 26 Million

Magenta 26 Million is a new interface for cryptograss communication, both between humans and other thinking entities. Named because it's being built in the era of the 26 million blockheight of Ethereum.

Basic pillars:

• A chat interface, not unlike discord, element, zulip, etc.
• Each chat "room" is coupled to a Motion, which in turn represents the context heap of zero or more LLM agents. Currently these are just Claude Code Sessions. Current sessions which can become Motions are `pickipedia-and-rabbithole`, `jams-and-events`, `delivery-kid` (maybe can be changed to storage and transfer), etc.
• Motions are publicly readable. Ideally, saved in the pickipedia database, as some kind of reachable text, so that links can exist from other pickipedia places (including semantic queries?) to conversations within Motions. Also, wikitext embedded in Motion chats needs to be legal / functional.
• Various tuning knobs for the AI aspect - including the backends (ie, models) and variables for those models (such as effort level) need to be available in the interface.
• Each discrete message needs to be tagged by the author, so that the agents can distinguish who is saying what.

Prior art

Things that already exist, so that we build less. None of these have been run by us yet.^[unverified]

• Alook — "rooms for people and agents". Apache 2.0. Discord-shaped; each person runs their own agent; agents carry a visible identity and owner; channel history is the record. Closest thing to these pillars.^[unverified]
• Agent Client Protocol (ACP) — open standard connecting any agent to any client. 25+ agents; adopted by JetBrains, Google, GitHub. Covers the backend-knobs pillar without bespoke work per model.^[unverified]
• AG-UI — standard event stream from agent to interface: streaming text, tool calls, state.^[unverified]
• assistant-ui — React chat components.^[unverified]
• AgentTeams — humans and agents sharing Matrix rooms; ships its own Matrix server. Matrix supplies accounts, rooms, threads and mobile clients without us writing them.^[unverified]
• Paseo — self-hosted, multi-harness, has voice. Per-user daemons proposed in maybelle-config#103.^[unverified]

Findings

• A Motion need not own a running process. claude -p --resume <id> continues one thread across separate invocations, and reads a name: prefix as attribution. Tested 2026-09-15.^[unverified]
• Attribution by session is already wrong: magenta.sh --join lets one person type in another's session, and memory-lane records it under the container owner. Per-message tagging fixes an existing bug, not just a future one.^[unverified]

Open questions

• Where identity comes from: wiki accounts, Matrix accounts, or our own.^[unverified]
• Whether a Motion's canonical record is the chat store or memory-lane. A chat log we can edit is a record we can corrupt and then trust.^[unverified]
• Motion granularity. A Claude Code session is a runtime instance, not a topic, and is not one-to-one with a context heap.^[unverified]
• Whether Motions get a registered namespace, so their volume can be filtered out of RecentChanges.^[unverified]
• How a Motion is summarised once it outgrows a context window.^[unverified]

Non-goals, for now

• Writing a chat platform from scratch.^[unverified]
• Writing an agent harness.^[unverified]
• Motions that run code. Talk first; execution needs a rights model.^[unverified]