You are reading a memo. Not a marketing page that looks like one — an actual memo in the MythOS library, written in the same editor you'd use, rendered live on this page. Edit the memo, and this page changes. That is the core mechanic of MythOS: everything you write can become a living page, readable by people and by AI. Here is everything the platform does, in the order your thinking moves: Memory, Mind, Mouth.

Memory — capture everything you write

MythOS starts where you already are: writing. Notes, journals, drafts, lists. The job of the Memory layer is to make capture effortless and make everything you capture connect.

An editor that links itself

Memos are markdown with superpowers. Type @ and link any memo to any other — the connection is permanent, navigable, and visible in your knowledge graph. Type # and tag a thought into a collection. Paste images like email. Collapse sections under headings. Templates give recurring memo types (meeting notes, references, reviews) one-keystroke structure.

Daily memos — journaling that compounds

A dedicated journal gives every day its own memo: a calendar, streaks, and habit tracking built in. Write 200 words and your "journaled" habit completes itself. Hashtags inside daily memos become searchable threads through your own history — click one and see every day you touched that idea.

Tasks, where you already wrote them

Any checklist in any memo becomes a task. The Tasks page aggregates every open checkbox across your whole library, and checking one off updates the source memo. No separate to-do app slowly drifting out of sync with your notes.

Bring your archive with you

Import from Obsidian and Substack — your post archive lands with publish dates preserved, images re-hosted, and paid posts kept private. Export everything, always. Your library is yours; MythOS holds it, it doesn't hold it hostage.

Mind — a library that thinks with you

Captured writing is potential. The Mind layer is where it becomes usable: connected, queryable, and readable by every AI you work with.

The knowledge graph

Every mention and fork draws an edge. The graph view shows your library as the network it actually is — focus on one memo's neighborhood, paint color groups by tag or date, save named views, and share any view by link. Orphan memos surface so nothing you wrote gets stranded.

Ask your library anything

Chat with your own writing. Questions are answered from your memos — with citations to the exact memo where you wrote the thing, not a model's best guess. Search works by meaning, not keywords. Bring your own OpenAI or Anthropic key, or use platform credits.

Built for AI collaboration

This is the part that makes MythOS different in 2026: your library speaks MCP. Connect Claude, ChatGPT, or Cursor and your AI reads, writes, and files memos directly — research a topic in a chat, and the result lands in your library as a permanent memo. Agent-discovery endpoints (llms.txt, an OpenAPI spec, a public API) make your public writing legible to every agent on the internet, on your terms.

Mouth — publish on your terms

What you've written and connected is worth sharing. The Mouth layer turns the same memos into pages, newsletters, and communities — without a separate CMS.

Every memo is a live page

Flip one toggle and a memo is public: a real page with SEO metadata, structured data, and your voice. Readers who land on it can chat with your library right there. Your profile is a feed of what you've chosen to share — a personal site that updates every time you write.

Newsletters from your library

Your subscribers live in MythOS too. Send any memo as an issue, run drip sequences, segment by topic, and let new readers subscribe from your pages. Moving from Substack? The import engine carries your full archive in, and your back catalog becomes something readers can ask questions of — not just scroll past.

Communities

Public spaces where creators gather around shared topics — post memos into a community, vote, discuss, moderate. A memo you wrote for yourself can become the seed of a conversation among people who care about the same problem.

Share with people, not just the public

Visibility is not binary. Contacts carry permission tags, memos carry audience tags, and the two meet so the right people see the right things — collaborators can co-edit, friends can read what's meant for them, and everyone else sees only what you've published. Forking lets others build on your public memos with attribution, like open source for thinking.

Start here

All of it begins with one memo. Free to start, no credit card, export anytime.