The project agent
The one assistant on a project page. Ask it about the project, or have it do the admin. It proposes; people decide.
The project agent is an AI assistant that works on one project. Ask it what is going on, go through your items with it, or have it do the admin: log your time, draft tasks, read a new document and stage what it changes.
The rule it follows is the same as everywhere in Delivery: it proposes, people decide. It never applies a change to the plan or settles a question. See Changes and review.
Open it
- Click Project agent in the project header.
- Press ⌘J (Ctrl J on Windows). Press it again to close.
- Use Ask the Project agent on a document in Knowledge.
- Notifications about your items can open a project with the agent open.
The agent opens in a drawer on the right. On a wide screen the page moves over to make room.
What you see
When you open it, the agent briefs you: Your items (your open tasks and questions, overdue first), the Next milestone, the Next meeting, what Needs answer, and what is To review. Below that, Try asking suggests starters that fit the project right now, such as Go through my items, What changed this week? or Stage what the latest document changes.
Type in the box ("Ask, or tell it what to update") and press Enter. You can drop documents into the box to add them to the project; the agent then reads them and tells you what they change.
Your chats are saved for you. New chat opens another tab, and History lists your saved chats so you can resume, rename or delete them.
What it can do
Answer questions, from the project's own data and documents:
- where the project stands, its plan, questions, RAID and status,
- what a meeting, email or document said, searching this project, its engagement and the BHG wiki,
- how BHG does something.
It grounds every claim in those sources and says so when they do not cover something.
Do your admin:
- Propose edits to tasks: mark done, reopen, re-date, retitle, describe, reassign, or move a task under a deliverable or milestone. Propose new tasks and who owns them.
- Log, list, correct or delete your own time on the project. Never anyone else's.
- List the team, and add, update or remove people (only for the project lead or a manager).
- Fix a change waiting on Events before the lead approves it: its owner, date, title or other fields.
- Find and attach evidence that a task is done.
- Send a short in-app notice to people on the project.
Bring in and read documents:
- Run Sync and report what each document changed.
- Find a meeting in your Granola account, or an email, calendar meeting, Teams transcript or SharePoint/OneDrive file in Microsoft 365, and copy it onto the project as a document. Connect these first on Knowledge Base › Connections.
- Work with the BRD and SOWs: report the BRD's status, start or continue a draft, promote a draft (lead only), list SOWs, and attach a Knowledge document to a SOW.
Stage plan changes for the lead: requirements, deliverables, milestones, decisions, test cases, the system build, meetings, agreements, RAID rows and the project dates. Before it stages anything from a document, it checks what the plan already holds and prefers updating an existing item to adding a near copy. Each staged change cites the document and an exact quote.
Record decisions as bundles: when you tell it the answer to a question, it stages the answer together with the plan changes the answer implies, for review. See Questions and decisions.
Undo: it can find a change in History and revert it. It always shows a preview first and reverts only after you confirm.
What it will not do
- It never applies or approves a change. When it stages one, you see a Staged for review card. If you are the lead, click Apply on the card (or Reject), or review it on Events.
- It never settles a question. A person applies the answer.
- It never sets project status or progress: they follow the milestones.
- Some actions run only after you say yes to that exact action in the chat: deleting a time entry, removing a team member, promoting a BRD draft, attaching a SOW document, notifying people and reverting a change.
It follows the project kind
The agent gets the operating instructions of the project's kind. On an Advisory it treats analysis as evidence and recommendations as decisions for the client. On an Implementation it checks that every requirement traces to a deliverable and a test case. On a Managed service it treats requests as tasks with service-level dates, and warns when hours used pass 85% of the hour block.
Long work
Some work, such as a Sync of many documents or a BRD draft, runs in steps. If a turn runs out of time, the agent tells you how far it got. Say "continue" and it carries on.
The engagement agent
Engagement pages have their own Engagement agent, with the same drawer and ⌘J. See Clients and engagements.