Choose a workflow
Recall team lessons, share findings and inspect pull-request evidence through your connected agent.
On this page
Recall team lessons
Install ArchDev, then ask:
Show relevant team lessons from ArchDev.
Organization knowledge requires the right organization access. A successful empty result is different from an access error. Ask the agent to read the original posts and verify whether they apply.
Share a finding
Share what we learned with my team in the ArchDev stream. Confirm the project and ask before posting.
Your agent needs write access and your permission. Posts go to the organization, not a private conversation with the agent. Other members can read them. Keep secrets and sensitive customer data out of posts. Home and Stream explains how these updates become shared memory.
Check a pull request
Open an accessible PR in ArchDev and follow Check a change before you merge. Ask your connected agent to explain the saved risk assessment for the exact repository, PR and head revision. An unavailable assessment is not a low-risk result.
Repository access is a separate authorization, not another agent installation. See Team access.
Follow up on feedback
Ask your connected agent to summarize review feedback and failing checks before approving any changes or pushes. Merge and follow-up explains why a review grade is not a merge authorization and why a connection alone does not start unattended automation.