What is June
June follows up on what stopped moving: it checks back when you said and brings a draft, a reminder or a question if nothing moved. What it does and where to start.
June follows up on what stopped moving, at work and for you. Tell it what should happen by when, or let it read the tools where the work lives. At that time it comes back, checks whether the thing moved, and if it has not, brings a draft, a reminder or a question to the same thread. That last step is what a plain AI chat does not do. You talk to June on the web, in the mobile app and in Slack.
SlackWhat that looks like
- An overdue invoice. A Monday check over the sheet where you track invoices, with its integrations turned on: "Invoice 2026-041 to Meyer GmbH is 12 days overdue. Reminder drafted below, in your tone." The draft stays a draft until you send it.
- The check on Friday. You answer "Friday", and ask June to check then and turn on its integrations. On Friday at 9 June looks at the invoice list again; if Meyer GmbH still has not paid, it drafts a firmer second reminder in the same thread.
- The morning readout. A schedule at seven, with its integrations turned on, that reads your connected tools and tells you what broke, what moved and the one thing waiting on you.
- The call you keep not making. You said Wednesday. On Thursday June brings it back, with the two questions you wanted answered drafted so the call is short.
A check June runs later reads your tools only when you ask June to turn them on for it (what a run can use).
What June does on its own, and where it stops
June reads, searches and drafts when you ask it to, and starts nothing new on its own beyond the follow-ups, reminders and schedules you set. A mail it drafts waits for you to send it. Follow-ups lists exactly where the line is.
What you can work with
- Where you talk to June: on the web, in the mobile app on iOS and Android, and in Slack.
- Mail: Gmail or any IMAP mailbox.
- Mail, calendar, chats and files: Microsoft 365 with Outlook, Teams, OneDrive and SharePoint.
- Files and notes: Google Drive, Notion, Obsidian, ownCloud and Nextcloud.
- Code, sites and posts: GitHub, Google Search Console and X.
- Your own machines: the devices on your Tailscale network.
- Anything else: any service with an MCP server.
iOS
Android
Outlook
Teams
OneDrive
SharePoint
Where to go next
Getting started
Sign in, start your first chat, and get June on your phone and in Slack.
Follow-ups
Ask June to check back and act if nothing moved; reminders and schedules.
Recipes
Step by step: chase overdue invoices, unstick pull requests, answer waiting mail, start the day, decide by Friday.
Chat
The composer, files, stopping and steering a reply, and keyboard shortcuts.
Integrations
Connect the tools June works in, and what it may do in each.
Memory
What June remembers about you, and how to make it forget.
Projects
A space for one piece of work, with its own instructions, files and memory.
Organizations
Work with your team in a shared space, with its own integrations and funding.
Models and who pays
Pick a model, and pay with June, your own ChatGPT or Claude plan, or an API key.
ChatGPT
ClaudeGoing further
What happens when you send a message, what June can do in a reply, June's sandbox, where a conversation lives, whose sign-in June uses and how schedules run.
Agents, Skills, Databases, Environment, and June MCP, to use your June connections from Claude Code, Codex or Cursor.
Codex
CursorHelp
- Security and privacy for who sees your chats, where your sign-ins are kept and what reaches the model
- Troubleshooting for the most common problems
- Support to report a bug or request a feature
- Limits for every number that bounds what June does
- FAQ for short answers to what people ask most
- Glossary for the words June and these docs use
The philosophy page explains why June is built this way.