AI and project context

Keeping files in Breeks starts building your project's memory. Titles, tags, linked records, and saved answers give that information more meaning for your team and its AI assistant.

Build context as you work

1. Keep project files together. Upload supported PDFs and images into Documents, under the appropriate type.
2. Make them findable. Check titles, document numbers, revisions, and tags.
3. Connect the information. Link an RFI to its drawing or marked region, and keep the answer on the record.
4. Keep work current. Update statuses and save decisions where the team can find them.

This gives the assistant stored project information to retrieve. It does not train a new AI model on your files. Current drawing tools use document details and available extracted text; uploading a file does not mean every page or detail has been understood.

Try it in Agent

Open Agent inside the relevant project. For example:

• “Find the current Level 3 fire protection plan.”
• “Draft an RFI: the duct route at Level 3 appears to conflict with beam B3. Ask the consultant to confirm the clearance.”
• “Assign RFI-0001 to Alex.” Use a record and member that exist in your project.

Check the saved draft and any suggested drawing. If several drawings could match, choose the right one or leave the draft unlinked.

Assignment and status changes appear as proposals. Confirm change applies the change; Reject dismisses it.

Shared project memory

Open Memory in the project sidebar to save a shared note, browse reports by folder, inspect their sources and download Markdown files. You can also ask Agent, “Remember for the project: the supplier reported delivery on Friday.” Notes are shared with project members and retain their authors and dates.

Project managers can enable individual connected groups in Project settings → Memory. Listening starts with new group messages, including messages that do not mention Breeks. It gathers reports without sending replies or changing records. Reports drawn from people who are not project members wait under Needs review and are not used by Agent until a manager confirms them. Pausing retains saved memory.

Reports remain labelled reported until a manager confirms them. Managers can correct or dismiss reports, and conflicting accounts remain visible. Formal records and current documents remain authoritative.

Private DMs and browser conversations stay private. Sharing an earlier discussion requires a note preview and your confirmation; only the approved note is shared.

Keep the team in control

The assistant works within your project access. Review drafts before using them and check the evidence behind suggestions. If Agent is unavailable, ask your administrator to enable it.

Automatic reminders need a project administrator to turn on follow-ups.

Next

Raise an RFI · Track tasks · Where Breeks is going