Monopea Calendar

Reads your week honestly, and rearranges it.

Availability, conflicts, recurrence and RSVPs — the deepest tool surface in the workspace. Changes land in your calendar where you can see them; the invitations are the part that waits.

Start free See pricing

.ics

Real file format, in and out

Agent tools behind this app

Approval gate for every outward action

CH · EU

Stored in Switzerland. Processed in the EU.

The Calendar app in week view, showing three overlaid calendars with a recurring standup, an all-day banner and overlapping blocks where meetings clash, beside a panel listing an event’s attendees and their RSVP states. — Calendar · three calendars overlaid on one week, and who has actually accepted

What you ask → what actually happens

Calendar, in the words people type.

Mechanism, not adjectives: each line is what the agent does when you say it.

“Find an hour all four of us have next week.”

Reads the actual calendars for free time and conflicts before it proposes anything.

“Move Thursday’s review to Friday.”

Moves it in your calendar, where you can see it and move it back. Telling the attendees is a separate, outward act — that one waits for you.

“Make it monthly, but skip December.”

Real recurrence rules with exceptions, not twelve copies of an event.

“Am I double-booked on Tuesday?”

Answers from the calendars you already keep, including the ones it only subscribes to.

Capabilities

What Calendar does.

Free time, for real

Reads the actual calendars for gaps and conflicts before it proposes anything.

Reversible writes

Moving an event writes into your calendar, where you can move it back.

Recurrence with exceptions

Monthly, but skip December — one rule, not twelve copies.

Subscriptions

Answers from the calendars you already keep, including the ones it only subscribes to.

Tools the agent calls

Real functions, not a chat reply.

Verbatim names from the runtime catalog. Every call is logged; anything outward is a proposal first.

calendar__find_free_time
calendar__check_conflicts
calendar__create_event
calendar__move_event
calendar__set_attendees
calendar__set_recurrence
calendar__set_reminders
calendar__set_rsvp

Governed

It works on its own. It asks at the door.

Inside the workspace the agent just works. Anything above the one risk threshold you set — and anything that leaves — becomes a proposal with its exact arguments, and waits for you.

How the approval gate works

Works with

The rest of the suite, one agent.

Meetings

Transcription runs in the browser, so the audio does not have to leave the machine. Summaries, actions and who-spoke-when come out of the transcript.

Explore Meetings

Mail

Accounts, threads, attachments and search in the same workspace as your files — the agent works from what it reads, and sending stays a thing you do.

Explore Mail

Teams

Members, roles and per-project scope, and agent personas with their own brief — the agent can run the workspace admin it is authorised for, and changes to who sees what are proposals.

Explore Teams

FAQ

Calendar, answered.

Does moving an event need my approval?

No. Calendar writes land inside the workspace and are reversible. Telling attendees is an outward act, and that part waits for you.

Does it send invitations?

Recording an attendee is not inviting them. Anything that reaches another person leaves the workspace and is held for you.

Can it read calendars I subscribe to?

Yes — subscribed calendars are part of what it checks for conflicts.

Does the agent need my approval for everything?

No — that would make it a form, not an agent. Work inside the workspace runs on its own; anything above the one risk threshold you set, and anything that leaves the workspace, becomes a proposal with its exact arguments and waits for you.

Hand Calendar its first job.

Open a workspace, give the agent a task, and approve what it proposes. Stored in Switzerland, processed in the EU.

Start free See every product