Everything your team dropped, sorted by 07:30.
Woodstock reads what your team drops into chat all day — photos, files, voice notes, links — and writes each person one short brief overnight. You skim it, and tap once where it needs you. That is the whole job.
Nobody files anything. They just drop it.
A photo on a loading bay, a voice note walking back to the car, a supplier PDF forwarded at midnight. Agent Organizer reads each one, says how much of it it managed to read, and files it onto the pages it concerns — which is why there is anything to brief you on in the morning. Try dropping something.
One photo of an invoice. Six moves. One tap from you.
A branch manager photographs an invoice on the loading bay at 07:12. Today that photo dies in a group chat. Here, the agents take it apart, check it against what the team already knows, and stop exactly once — at the decision only a human should make.
$470 above the quote Daniel sent in August. Same line item, different unit price.
Run the cascade to see what Agent Accounting asks for.
One question, once. Agent Accounting read the photo, found the purchase order, compared it to the quote and drafted the payment on its own. It stops here because this is the only moment where money actually moves — and the answer you give is kept beside the invoice, so “why did we pay that?” has an answer in December.
Pick a topic. Watch what already knows about it.
Everything the team drops resolves into the same people, companies, projects and documents. Choose what you care about and the network lights up around it — including the part your team knows and you don't.
One person drops it. Someone else uses it.
A personal assistant knows what you told it. That is the ceiling — and it is why AI has made individuals faster while teams stayed exactly as slow as before. Follow one fact through three days and three people, then flip the switch and watch the same week without a shared brain.
And the same night becomes a different brief for each person.
The owner, the finance lead, the site manager and the person who joined on Monday all wake up to one short read — each built from the same knowledge, each written for the one person reading it. Pick anyone.
What you skip stops appearing. Mark a block “not useful” and it drops out of your brief tomorrow — and only yours. Nothing is deleted; it just stops being shown to the one person who never reads it.
Four teammates who never miss a drop.
Named, @-mentionable, and in the workspace on day one — nothing to install, no keys to paste, no prompt to write. Each one arrives with skills: plain jobs you can hand it, the way you would brief a new hire. Pick an agent, then pick a skill to see what it actually does.
No agent reaches past what the person who invoked it is allowed to see. Calling a different agent is never a way around your own permissions.
No delete in the app reaches a drop. The file, the message and the record of where it arrived all survive — a brain that can lose things is not one you would fill.
What lands in a private channel is answered there and nowhere else. It changes no shared page and never surfaces to a teammate asking a similar question.
A PDF, a scan, a web page is evidence, not authority. Text inside a file can inform an answer; it can never make an agent act, widen access, or send anything out.
What is real today, and what we are building next.
You are looking at a vision page. Here is the honest split — so you can judge the direction, not just the demo.
- Drop → read → file. Files, photos and links become pages, with the page count as proof it was read.
- Pages with history. Wiki-style updates; a line a person wrote is never overwritten.
- Ask days later. The agent re-opens the file instead of answering from memory.
- Per-channel capture and read-only GitHub & Linear as outside sources.
- Capture from LINE and WhatsApp, so frontline staff never learn a new app.
- Cold-start import — your last three months of chat and one Drive folder, before day one.
- The 07:30 brief, written per person and tuned by what you skip.
- One-tap approvals and write-back into accounting and calendar tools.
- Relationship strength — who on the team has the warmest, most recent line to a supplier or client, scored and decaying with time.
- Agent to agent. Your coding agent hands work to the workspace and back, and you watch it happen.
- Canvas channels where humans and agents build the thing together instead of trading messages.
- Cheap by design — small models for the boring 90%, so a workspace costs less than a part-time hire.
Point it at the group chat you already regret.
One branch, one client, one project. Bring this month's files, drop them in, and ask it something real on Friday. If the answer is right, the workspace has already paid for the afternoon.