Claude Duet can prepare project follow-up drafts and morning briefs from connected sources. For architects, a useful trial is a short review queue that identifies what needs a decision, what needs clarification, and what is ready to inspect. Those states help organize coordination without treating a new message as approval to change a model.
What is Claude Duet, and who can access it?
As of November 4, 2026, Duet is a US‑waitlisted research preview for Claude Pro, Max, and Ultra accounts (not Team/Enterprise). It runs a cloud computer that uses your existing Claude memory, skills, and only the connected apps you authorize; it prepares morning briefs and background follow‑ups from those sources and surfaces drafts when you return. Checks are periodic, not real‑time monitoring. It cannot see local files, and Microsoft 365 (SharePoint/OneDrive/Outlook) is unavailable in this preview. Before sensitive steps, Duet is designed to ask for approval—treat that review as required practice. See the official notes in Get started with Claude Duet and the Duet overview.
How Duet can prepare an architecture project morning brief
Start with one project and the connected correspondence or documents approved for the task. Identify where decisions are recorded and which people can confirm them. Ask for a source link and an unresolved question beside every proposed priority.
A hypothetical morning brief might contain three items:
• Needs designer approval: a lobby ceiling-finish proposal awaits a decision from the architectural lead.
• Awaits clarification: a message refers to a revision on A-102, but the referenced issue and changed area are unclear.
• Ready for review: a supplied schedule extract is available for comparison with the current project record; it has not been accepted.
These are proposed review states, not findings Duet can enforce through labels. Check them against the source material. A schedule extract may omit relevant filters or context, and a confident message may still refer to an older issue.
Keep the brief useful by identifying the next person and question for each item. “Waiting on supplier” is less actionable than “Project architect to request the revision date of the supplied A-102 export.” The example does not imply that Duet has queried Revit.
Example: follow a coordination question without approving a change
Suppose a coordinator writes, “Plan updated—see the revision tag on A-102 for the lobby area.” The sheet number is present, but there is no attachment, issue date, or clear identification of the changed area.
Ask Duet to summarize that gap and prepare a clarification draft. The useful question is which issue of A-102 the message refers to, where the change appears, and where the recipient can inspect the referenced export or sketch. Requesting a Revit element ID would be unnecessary if the sender only has the issued PDF.
Keep the original message attached to the proposed follow-up. The assistant should not infer that the most recently accessible A-102 file is the intended issue. If its connected sources do not include the attachment, it should say that rather than conclude nobody supplied one.
When the sender supplies the referenced export, the proposed status becomes “ready for review.” The project reviewer checks its identity and scope. If a design choice remains open, the item moves to “needs designer approval,” with the decision owner identified. Receiving a document has resolved an evidence gap, not necessarily the design question.
After a decision, the team can prepare a separate model instruction with the approved source and affected scope. Duet's role in this example is correspondence and preparation; these are proposed team procedures, not a documented Revit integration.
Claude Duet vs Cowork for files and project work
Cowork runs cloud task sessions; for local files or computer/browser actions it relies on the connected Claude Desktop app being open. It supports project instructions and plugins. Ordinary file access does not itself establish a Revit API connection. Duet runs proactive background checks from approved connected apps. See Get started with Claude Cowork.
Practical use
• Duet: morning briefs and follow‑ups pulled from the sources your team approved, with clear labels (needs designer approval; awaits clarification; ready for review).
• Cowork: a defined task such as reconciling a PDF set with a register, producing a spreadsheet, or assembling a document from approved files. Its cloud task sessions do not require you to drive every step interactively.
Can Claude Duet control Revit?
The reviewed Duet docs do not establish direct control of Revit models; keep BIM edits a separate, human‑governed step. If your team needs an AI teammate that can create/update native Revit and AutoCAD elements and produce documentation on Windows, evaluate ArchiLabs Desktop. For context on what’s realistic in Revit‑adjacent AI today, see Revit 2027 AI Review: What’s Real, What Still Isn’t and where automation belongs in practice in AI‑Powered Revit Automation.
Pilot a single‑project morning brief. Define the three labels, point Duet at the approved sources, and review one drafted brief per day—tuning what qualifies for each label and who signs off before any model work is scheduled.
Honest review of Revit 2027 AI: placement, docs, generative design, clashes, Forma links—what saves time, what’s half‑baked, and gaps.
Boost Revit productivity with AI-driven automation: generate models, check errors, streamline workflows, and save time across BIM projects.