Follow-ups

Ask June to check back on something at a time, and to act if nothing moved. At that time it works again in the same thread: it looks at what you pointed it to, and if the thing is still stuck, it brings the draft, reminder or question you asked for.

Name a time zone if it matters ("9:00 Berlin time"). Times work to the minute.

What a check can use

A check or schedule June sets up from chat runs without your tools by default: it answers from its instruction and what June remembers, not from your mail, files or the web. Ask June to turn on the toolsets it needs, by name:

• integrations: the tools on your Integrations page, such as your mailbox, Microsoft 365 or Notion
• web: web search
• documents: Google Docs, Slides, PDFs and images in your Google Drive
• terminal: June's sandbox, including GitHub as you, wherever the schedule was set up

On the New schedule form, list them under Enabled toolsets. How schedules run has the rest of what a run can use.

Reminders

A reminder is a message June brings back at the time you named. It does no new work when it fires; for a check, ask for a follow-up as above.

Say when in plain words: a time, a day, or "in two hours". June posts the reminder in the thread where you asked and notifies your devices.

Schedules

A schedule repeats a piece of work: "every Monday at 7", "every 30 minutes", "on the 25th of every month". Each time it runs, June reads, searches or checks what you described, with the toolsets you turned on for it, and posts what it found.

A follow-up, reminder or schedule replies in the thread you asked in. If June is in your Slack workspace, ask for Slack and it posts there instead.

The Schedules page

The Schedules page lists everything June does for you at a set time: what needs attention because its last run failed, what is coming up next, what is paused, and what is already done.

Each schedule's menu has:

• Run now: run it once, now.
• Pause and Resume: stop it until you resume it. Resuming picks a new next run.
• Open history: its past runs.
• Delete: it stops and leaves the list. This cannot be undone.

You can also ask June in chat to list, change, pause or remove a schedule. New schedule opens a form for setting one up by hand. How schedules run has the exact rules: time zones, missed runs, who pays and what a run can use.

What June does on its own, and where it stops

June works on what you ask, in the thread where you ask. Work it does later is a follow-up, reminder or schedule you set.

Once you ask, June goes ahead and:

• reads and searches the web, the files you attach, and the tools you connected on the Integrations page
• drafts replies, messages and documents for you to send or use
• runs code in its sandbox, its own workspace in the cloud
• saves what it learns about you as memories
• leaves comments on GitHub when you ask, as you, in your own and an organization's chats and in Slack
• starts a separate thread for part of the work, on the web and in the app

June stops short of:

• sending mail. In a mailbox you connect, June writes drafts; you send them.
• steps that need your confirmation, such as creating a Microsoft 365 calendar event or sending a Teams message. They fail today, in every place (why).
• commands that could do damage. Its sandbox refuses commands such as wiping a disk or running a script piped straight from the internet (the full list).

What follow-ups do not do

• A schedule does not run more often than once a minute.
• A schedule cannot set up further schedules.
• A check does not read your tools unless you turned its toolsets on.