How June collects and organizes memory

This page is for when you want to know exactly why June remembered something, or did not: when it saves, how much, what it brings into a reply, and where each memory lives. Memory covers the everyday use.

What June keeps

Which memory each place reads and writes

A Slack channel's memory is shared by every thread in that channel and seen by no other channel. An organization's chats outside its projects share one memory.

When June saves on its own

In a chat on the web or in the app, June looks back over the conversation 10 minutes after its last reply. Each new reply starts the wait over, so a busy chat is looked at once it goes quiet. The look-back covers everything said since the last one; a long backlog is read in parts of about 200 messages.

It saves a memory only when something passes every test:

• Someone said it. Only messages people wrote count, never June's own replies or guesses.
• It lasts. Still true and useful months from now, in a chat about something else.
• It stands alone. Readable without the conversation around it.
• It is one of five kinds: a standing preference, a fact about who you are (your role, where you are, what you know), a decision or commitment, a rule for how to work with you, or a fact about a person, team or company you work with.

June scores each candidate from 1 to 10 for how much it would change later answers, and drops anything below 5. Each look-back (each part of a long one) saves at most 2 new memories. June does not save questions, tasks, work in progress, passing details ("running late today"), secrets or commands. Most chats save nothing, and that is on purpose: every memory competes for room in later replies.

Before saving, June compares each new fact with the memories it already has in that place. It then does one of these:

• Adds it when it is new.
• Updates an existing memory when the new fact refines or corrects it. The old wording stays in the memory's history.
• Forgets an existing memory that the new fact plainly contradicts.
• Keeps a memory that already says the same thing, and notes the new chat as one more place it was said.

The same look-back also decides whether your Soul should change (below).

This work runs on a small model and is paid for the way your chats in that place are (Models and who pays). The Usage page lists it as background work. If the place's funding source cannot pay, June skips the look-back.

When you ask

When you ask June to remember or forget something, it acts at once:

• Guidance for every chat. Your name, how you want replies, a standing rule: June puts it into the place's Soul (which one). In Slack, where June changes no Soul, it becomes a memory.
• A specific fact. June saves it as a memory now, without the scoring above, in up to 240 characters. Asking it to remember the same words again (case and spacing aside) adds the chat as one more place it was said; a reworded version becomes a second memory.
• Forget. June searches the memory of the place you are in and forgets the single closest match, if it is close enough; otherwise it says it found nothing. To forget several things, name each one. Asked to drop something from the Soul, June takes out the matching lines and keeps a new version.

How your Soul is built

A Soul is an ordered list of short statements, each one plain paragraph of at most 120 words. The whole Soul holds up to 3,000 words. June merges and rewords statements to stay under it rather than cutting any off, and a change that would go past it is not saved.

• Every change is a new version. June never edits a version in place. The Memory page lists the latest 100 versions.
• On its own, June only adds and rewords. It takes a line out only when someone asks. It changes a Soul on its own only in your personal chats and your own projects; an organization's Soul, and the Soul of an organization's project, change only when someone asks.
• What belongs in it. Your Soul holds how to address you, how you like answers, long-lived goals or conditions, and standing rules June would get badly wrong without. Specific facts are memories instead.

A project's Soul holds what the project is, its conventions and the decisions that stay decided. An organization's Soul holds the same for the organization. June keeps one person's preferences and personal facts out of both.

What June brings into a reply

For each reply on the web or in the app, June reads:

• The Souls of the place, in full: yours in a personal chat; yours and the project's in your own project; the organization's (and the project's, in one of its projects) in an organization's chat.
• Up to 8 memories that fit your latest message. June weighs how closely each one matches, how recent it is and how much it scored, and keeps the best within about 2,000 words. If nothing matches well, it brings none.
• Short notes on the last 6 exchanges in the same place: what was asked and how June began its answer, so it can pick up where another chat left off.

The 3 memories in context line above a reply counts a memory from a place you cannot see on the Memory page without naming it.

In Slack, June reads the newest 12 memories of the place every time, plus up to 8 that fit the message, and no notes from other chats.

Shared chats

An organization's chats and projects, and Slack channels, are shared chats. Each keeps a memory of its own, a room memory, which June uses for everyone it answers there. That shapes what June keeps:

• Shared facts only. June saves decisions, project status and shared context. It keeps a person's health, family, private preferences and biography out of a shared chat's memory and Soul; asked to save one there, it suggests a personal chat or a direct message instead.
• Your personal memory stays out. June never reads your personal memory or your Soul in a shared chat, and never writes a shared chat's facts into them.
• Names. When June replies in a shared chat, it sees each person's name beside their message. When it looks back over one to save memory, it reads the messages without their authors' names, so it keeps what was decided rather than who said it.
• Notes from other chats. In an organization, the notes on recent exchanges come from all of its chats outside projects (or from all chats of the project), so June can pick up what a teammate asked in another thread.
• Who can forget. Everyone in an organization sees its projects' memories on their Memory page and can forget them there. An organization's own memory and a channel's are not on the Memory page; ask June there.

What forgetting keeps

A forgotten memory keeps its history and comes back only if someone says it again (Forget a memory). Two more things stay:

• Soul versions. Removing a line from a Soul makes a new version; earlier versions still show the line in the version history.
• The notes. Forgetting a memory does not touch the short notes on recent exchanges. They drop out of replies as newer exchanges come in.

Where a memory came from

June records each message that stated, refined or restated a memory or a Soul line. The Memory page turns that into a line such as said in 3 chats · first Oct 4, 2026 (see where June learned something).

Ask June how it knows something, and it looks first at the memories and Soul lines in front of it, then searches the memory of the place. It links only chats you can open; in an organization's chat, only chats everyone there can open.

What June does not do

• It does not save on its own in Slack, in a direct message or a channel.
• It does not let you see or edit the notes on recent exchanges.