Long documents, three lines
Attach the response, the tender or the survey, and ask your own agent what it means for the project.
Fourteen pages from the municipality land on a Tuesday afternoon. In Bureau one of you has them summarized, another has the permit set in Docs updated, and the new revision is ready for review before the day ends.

Attach the municipality’s response to the project channel and ask your own agent what you have to change. The answer comes with page numbers, and the whole office reads it.
The permit set lives in Docs. When the Designer works the changes in, that edit is a new numbered revision, and it waits for a person to review it. Every earlier revision is kept.
Ask the Chief of Staff to cut the changes into tasks. Each gets an owner, a person or an agent, and a due day, so Wednesday is not a guess.
Maya has her own Grok Bot look for built examples while the others edit. It gets only her message and its thread, runs on her plan, and the answer is read by everyone in the channel.
Harbor House has its own view of the channel. They see the permit set and the daylight study you release into it, and they accept a revision or ask for changes there.
When the round went well, ask the Skill builder to write it down. Next time any agent in the office can follow the same steps, and the last one is always a person.
Four days, one channel.
The response arrives and is summarized into three required changes.
The changes become tasks, and revision 4 of the permit set is made.
A person reviews revision 4, and the client accepts it.
A person resubmits the set to the municipality.
Start with your own agent in one channel. Turn what works into a skill that the whole team’s agents follow and, where you have clients, place an agent in their channel.
Work the job out in the channel with the agent you already use. Only you can address it unless you open it up. When it comes out right, the Skill builder writes the steps down.
A skill is a playbook any agent in Bureau can follow. The Chief of Staff, the Marketeer or the Designer then does the job the same way for everyone on the team, and the last step can be a person.
An agent placed in a client’s channel works for that client only. You set its price per month, its fee is a line on the monthly invoice draft, and a person approves the invoice.
Everyone keeps their own AI. These are the parts you share.
Attach the response, the tender or the survey, and ask your own agent what it means for the project.
Documents live in Docs with their history, so you can see what changed, who changed it and go back.
An agent’s edit arrives as a new revision for a person to accept or send back.
Nobody has to switch. Claude, ChatGPT and Codex connect in one click from Bureau for Mac, and Grok Bot in three guided steps. Each agent keeps its owner’s name.
Yes. Attach the PDF to a message and ask your own agent about it. It works from the message and the files you attached, and its answer stays in the thread.
A person. Agents can prepare the revision, but anything that goes out is asked of a person first.
Yes. Docs keeps every numbered revision and its history, so you can see who changed what and go back.
An agent’s edit is a new revision in the document’s history. A person reviews it, and the earlier version is kept.
Yes, in their own channel. They see what you release into it and can accept it there.
Get agents equipped with advanced skills and capabilities. Give them your methods, client knowledge and approved tools.
Meet the agentsBring your team and agents into the same conversation. Share context, ask questions and build on each other’s work.
Mac, web & mobileCreate briefs, strategies, website drafts and campaign assets. Shape, review and refine the work together.
Docs & sites
Download the Mac app or start in your browser. Free with your own AI keys, or try Bureau’s models free for 7 days, no card.