Glossary | June Docs

The words you meet in June, from threads and shelves to integrations, memory and funding sources, defined in one place.

The words below are the ones you meet in June and in these docs, defined the way June uses them.

The first mention of a term on any other docs page links back here, with the definition on hover, so you rarely have to leave the page you are on.

Conversations

Pin: A pinned thread stays on the Pinned shelf at the top of the sidebar until you unpin it.
Settlesettled · settling: Settling a thread says you are done with it for now: it moves to the Settled shelf, and “Unsettle” brings it back. Threads you leave quiet can settle on their own; choose after how many hours under “Settle after” in Settings.
Share linkshare links · shared link · shared links: A link to a conversation that anyone who has it can read, up to its 500 most recent messages. It shows the conversation as it was when you shared it, unless you turn on “Auto-update”. Delete the link to stop sharing.
Shelfshelves: The sidebar sorts your threads onto three shelves: Pinned, Active and Settled. A thread moves between them as you pin it or settle it. To see one project's threads, filter the sidebar by that project.
Steer: A message you send while June is still working on a reply. June reads it at its next step and adjusts, without starting over. Once you type during a reply, the send button turns into “Steer”.
Threadthreads: One conversation with June. On the web and in the app every chat is a thread; in Slack, a DM or a Slack thread is one. A reply in thread, or a thread June starts from another one, sits under the thread it came from in the sidebar.

Channelchannels: A place where you talk to June: Slack, the web, or the app on your phone. In Slack, a channel is also Slack's own word for a shared room; June answers there when someone mentions it.
Integrationintegrations: A connection to one of your tools, such as your mailbox, Google Drive or GitHub, that lets June read from it or work in it when you ask. You connect and disconnect each one on the Integrations page, and each one says what June may do there.
June MCP: June's own MCP server. Add its address to Claude Code, Codex, Cursor or another MCP client and sign in with your June account, and that tool can use the integrations you connected in your personal space. It gets no chat with June, no memory and no threads.
MCP clientmcp clients: An AI tool that can use the tools of MCP servers, such as Claude Code, Codex, Cursor or OpenCode. Add June MCP to one and it can use your June integrations.
MCP servermcp servers · mcp: A service that offers its tools in a standard format (the Model Context Protocol). Add its address on the Integrations page, sign in if it asks you to, and June can use its tools in your conversations. Remove it and June loses access.

Memorymemories: What June keeps from your conversations so you do not have to repeat yourself: facts, preferences, decisions. The Memory page lists what it saved and lets you search it; “Forget” removes a memory. Memories cannot be edited.
Projectprojects: A space for one piece of work: its own instructions, files, memory and chats. A chat you start in a project uses its instructions and files, and what June learns there stays in the project.
Room memory: Memory that belongs to a shared chat instead of one person: a Slack channel, an organization's chats, or an organization's project. June uses it for everyone it answers there, so it keeps personal facts out of it and never mixes in anyone's personal memory.
Soul: The lasting context June carries into every personal conversation: your stable preferences and personal context, shaped as you talk. The Memory page shows the current version and what changed in each earlier one. Projects and organizations have a Soul of their own.

Reminderreminders: A message June sends you at a time you asked for, in the conversation where you asked. Ask in plain words, for example “remind me Friday at 9 to send the invoice”.
Scheduleschedules · scheduled job · scheduled jobs: Work June does at a set time: once, to check back on something and act if it has not moved, or on a repeating timetable, such as a Monday readout over your connected tools. Ask for one in chat; one set up there runs without your tools unless you ask June to turn on toolsets such as “integrations” or “web”, or list them under “Enabled toolsets” on the form. The Schedules page lists them and lets you change or stop each one.

Mentionmentions: Typing @ and a name tags someone in a shared chat. In an organization chat June answers only when tagged with @june; in Slack channels, only when mentioned.
Organizationorganizations: A shared space for a team. Members chat with June together, use the integrations connected for the organization, and can have one funding source pay for everyone. Members are Admins or Members; invite people by email address (you send them the link), or let anyone with your company's email domain join.

Funding sourcefunding sources: An API key, or a plan an admin shares, that pays for every turn in a space in place of each person's own plan.
Modelmodels: The AI model that writes June's replies. Pick it in the composer: some come with June, others run on your ChatGPT or Claude plan or on your own API key.
Reasoning effort: How long the model thinks before it answers. Higher effort is slower and suits harder questions. Pick it next to the model in the composer; not every model offers every level.

Agentagents: An AI that works in steps toward a goal, using tools, rather than answering once. June is one. On the Agents page you can design your own for one job; it answers from its persona, instructions and skills, without tools.
Sandboxsandboxes: June's own workspace in the cloud, where it runs code, works on files and uses command-line tools such as git while it works on your request. It is not your computer.
Skillskills: Written instructions for one kind of task, which June picks up when that task comes up. The Skills page lists the skills you have.