What is June
Learn to use June: get a useful first answer, work with files and connected tools, and set follow-ups.
June helps you move work forward: draft a reply, understand a file, check your connected tools, or come back to something at a time you choose. You can talk to it on the web, in the mobile app, and in Slack.
New to June? Start with your first chat. You will get a useful draft and refine it, without connecting any tools.
What do you want to do?
Get your first useful answer
Give June one task, review the result, and make it yours.
Understand a file
Read a document, compare price lists, or turn a table into a file.
Work with your tools
Connect the account June should use, then ask about your mail, files, or work.
Bring something back later
Set a reminder, a check, or a repeating piece of work.
See a task take shape
Say what you need, with enough context to start
Name the invoice, how late it is, and the tone you want. You do not need a connected mailbox to get a draft.
Draft message: Draft a friendly payment reminder for invoice 1042. It is twelve days overdue. Ask when payment is expected, keep it under 100 words, and leave the customer name for me to fill in
An example with sample data. No messages are sent.
Try a complete workflow
Pick a recipe when you want the whole path, including what to connect and what to check at the end: chase invoices, prepare for the day, or make a decision by Friday.
What June does on its own, and where it stops
June reads, searches and drafts when you ask it to. A draft stays a draft unless you ask it to send through a service that supports sending. Changes to your connected tools follow your approval rules; reads do not ask.
Work you want June to repeat or return to needs a follow-up, reminder or schedule. 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.
Explore the handbook
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.
Settings
Approvals: which changes June may make without asking, which must ask, and which are blocked.
Going 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.
Find the answer you need
Search the docs for the action you want to take, or the words you see in June. Each page offers a Markdown version and a way to ask June about that page. Standalone example prompts open as editable drafts; examples that depend on an existing conversation offer copying into that chat instead.
For a quick distinction between terms, use the glossary. For exact size and timing boundaries, use Limits. If something failed, start with Troubleshooting before repeating an action that might already have completed.
Help
- 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.