The power path
Claude Cowork and your event folder.
Claude Cowork is Anthropic's agentic work surface: the same architecture as Claude Code, with no terminal to learn. You give it a folder of your own material and it works through it with you. Details are on Anthropic's Cowork page.
This is the power path, not the default. Cowork is on paid plans only (Pro, Max, Team and Enterprise), and although it runs on desktop, web, mobile and the Chrome side panel, reading files on your computer only works on the desktop app. Connectors and Skills work on every surface. See using Claude Cowork on web, desktop and mobile.
The default way to run Presso is simply adding the connector, which works on a free Claude plan and on a phone. Come here when you already keep event material in files and want your AI to read it.
The boundary, and it matters
Two things are in play, and they are not the same thing.
- Presso is the system of record. Everything reached through the connector lives on Presso: your events, ticket types, orders, ticket buyers and check-ins. That data changes on its own, every time somebody buys a ticket or walks through the door, and no folder on your computer knows it happened.
- Your folder is raw material. Your brief, your ticket plan, your agenda notes, your speaker bios. It is what you would have typed in by hand. Your AI reads it and fills in Presso for you.
Never keep event data only in local files as a second copy. A file saying you have sold 40 tickets is wrong the moment the forty-first sells, and you cannot run a door off a laptop. If it is a fact about what has happened, ask Presso. If it is something you decided and wrote down, it can live in the folder.
Presso never sees your folder. Your AI reads it on your machine and sends only the values you ask it to save.
The folder convention
One folder per organiser, not per event. Events come and go inside it. Everything is Markdown (plain text files ending .md) because a human edits these, sometimes on a phone.
Presso - Rivera Events/
brief.md dates, venue, capacity, what the event is
tickets.md types, prices, quantities, sale windows
agenda.md sessions: time, title, room, speaker
speakers/
ada-lovelace.md name, title, company, bio
ada-lovelace.jpg
assets/logo.png
The filename stem is what joins a speaker to their photo: ada-lovelace.md and ada-lovelace.jpg are the same person because the names match. Keep them matching and you never have to explain which picture belongs to whom.
Nothing here has to be tidy prose. A few bullet points per file is enough, and half-finished is fine: your AI will ask about anything it needs and cannot find.
A first session, start to finish
Open Cowork on the desktop app, point it at your folder, and make sure the Presso connector is added (see adding the connector). Then start with something like this.
Read everything in this folder, then tell me what you have and what is missing before we create anything in Presso.
What happens: Claude reads your files and reports back. It should tell you the dates and venue it found in your brief, the ticket types and prices in your ticket plan, how many speakers have bios, and which of those are missing a photo. Nothing has been sent to Presso yet.
When the picture looks right, let it build the event.
Create this event in Presso from the brief, add the ticket types from tickets.md, and add the speakers and the agenda. Leave it as a draft, do not publish.
What happens: Claude uses create_event for the event itself, ticket_types for the prices and quantities, add_speaker for each person in speakers/, and set_agenda for the sessions. It will stop and ask rather than guess a price, a capacity or a venue you have not written down.
Then check it before it goes live.
Read the event back to me from Presso and tell me anything that does not match the folder.
What happens: Claude reads the event and its agenda back out of Presso with list_events and get_agenda and compares them with your files. Publishing stays a separate, deliberate instruction, because publishing is the moment an event becomes payable.
Keeping it honest week to week
Once tickets are on sale, the two sides drift apart in one direction only: Presso moves, the folder does not. So the weekly habit is to compare, not to copy.
Compare the agenda and speakers in this folder against the event in Presso, list the differences, and ask me which side is right before changing anything.
What happens: Claude reads both and shows you the gaps. You decide each one. It should never overwrite the folder with sales data or overwrite Presso with a stale note.
For anything about money or people who have bought, ask Presso directly rather than looking in the folder. Sales, revenue, the attendee list and the door are all live questions, and the prompt library has the wording.
If Cowork is not available to you
You lose nothing that matters. The connector on its own does the whole job, and it works on a free Claude plan, in a browser, on a phone. The folder is a convenience for people who already work in files.