Skip to main content
MythOS
Since 2017

We've been thinking about memory longer than the models have.

MythOS started as a question: what happens when the thing you're remembering for keeps changing? A new journal. A new app. A new model. Your notes move; your thinking doesn't. We built MythOS so it finally could.
The tools changed. The AIs changed. Your memory shouldn't have to.

— Why we built MythOS

Origin · 01

From a notebook to a protocol.

In 2017, MythOS was a personal system — tags, mentions, cross-links, all in Markdown. The point wasn't to build an app. The point was to never lose an idea again.

Then the models arrived. ChatGPT, Claude, every successor. Each one asked the same questions: who are you, what do you think, what have you already written? And every time, you had to start over.

We kept watching people paste the same paragraph into every new chat. Rebuild the same context. Re-explain themselves to a machine that already had access to the most advanced language understanding in history — but not to them.

So we turned the notebook into a protocol. MythOS is the missing layer: a library that lives outside any one model, addressable by all of them.

Doctrine · 02

Memory. Mind. Mouth.

Every thinking person already has these three systems. Most are scattered. We organized them.

Memory is the library: every memo, every hashtag, every link. Markdown by default so it survives everything.

Mind is the layer that makes the library think back. Chat with your memos. Let agents orchestrate them. Every answer grounded in your own words.

Mouth is the public-facing half: publish a memo, send it as a newsletter, host a conversation, get surfaced in search — human and machine.

The goal is not a note-taking app. The goal is the connective tissue between how you think and how you show up online.

The long road to now.

2017

Personal experiment.

The name "MythOS" first gets written down — a Markdown system for permanent personal context, pre-dating the LLM era by five years.

2020

First public memo.

Content doctrine firms up: mentions, hashtags, automatic backlinks. The library starts thinking in graphs without anyone calling it one.

2023

The model flood.

ChatGPT, Claude, Gemini, and a hundred open-source models arrive. We rebuild MythOS around a single truth: no one is going to win, and your memory shouldn't pick a side.

2024

Portable context.

MCP server, Agent API, /llms.txt . Your library becomes addressable from any model, any agent, any script.

2026

MythOS v5.

Memory. Mind. Mouth — one library, six surfaces. The current product — and the one this site mirrors.

What we will and won't build.

01

Yours, forever .

Every memo exports to Markdown. Every library survives us. If we ever stop existing, you still have everything.

02

Model- agnostic on purpose.

We will never bind your memory to one vendor's model. Today's best LLM is not next year's. Your library outlives both.

03

Private by default .

Everything starts private. Public is a toggle you own, per memo. We don't train on your library, and we don't sell your context.

04

Craft over features .

The editor has to feel like paper. The agent API has to feel like curl. Fewer, better primitives — not a dashboard of half-finished modules.

05

No ads. Ever.

You pay, we work. That is the entire economic model. Your attention is not a revenue stream.

06

Open where it counts .

Schemas public. Export tools open-source. /llms.txt discoverable. Portability is a feature, not a favor.

Who's building this.

A small team. Writers and systems people who've been doing this long enough to care about the shape.

BS

Brian Swichkow

Founder · Writing

Started MythOS as his own memory in 2017. Still maintains the flagship public library at mythos.one/me/brianswichkow .
AK

Asha Kaur

Engineering · Platform

Builds the capture and Mind layers. Previous work on graph stores and real-time sync.
RM

Reza Molina

Engineering · Agents

Wrote most of the MCP server. Thinks about portable context at a depth most people find uncomfortable.
JN

Jade Nakamura

Design · Editor

Designs the editor, the feed, and the public-memo reader. Believes writing tools should disappear.
TO

Tomás Okafor

Community · Support

First stop for Scholar and Oracle customers. Runs the community space and office hours.

You, maybe?

Hiring · 2026

We hire writers who can ship and engineers who can write. Drop us a note →

Come build a library that remembers you back.

Create Your MythOS