AgentPM
Sign inSign up

// data collection

How AgentPM collects data.

AgentPM collects configured coding-agent work context so you and your team can review what happened, what changed, and what still needs attention. Users decide what AgentPM can access, where collection happens, and how broad or narrow that access should be.

What can be sent

  • Coding-agent prompts, responses, and session history
  • Commands, tool output, and development steps captured during the agent workflow
  • Project, repository, file path, and environment context inside approved boundaries
  • Agent, organization, project, and timestamp metadata needed to organize the work
  • Decisions, risks, open questions, and handoff notes that appear in the workflow

What gets stored

  • The work records needed to review, search, and understand agent-assisted development
  • Associated labels such as organization, project, repository, agent, and session
  • Summaries and review context that help teams find decisions, changes, risks, and follow-up work
  • Collection settings and boundaries chosen by the user

You control the scope.

The data is yours

AgentPM treats collected work context as your data. It exists to help your team understand its own work.

You choose the scope

Collection can be limited to specific servers, home directories, project folders, repositories, or other configured boundaries.

You can change it

Teams can remove access, restrict collection, or update boundaries as projects and policies change.

What the data is used for

AgentPM is meant to make agent-assisted development easier to review and manage. It is not designed to track activity outside the configured agent, project, or environment scope.

  • Reconstruct what happened in an agent-assisted development session
  • Understand why a change was made and what context the agent had
  • Preserve handoff context between developers, agents, reviewers, and leaders
  • Surface unresolved work, risky changes, repeated friction, and useful patterns

Changing or removing collection

If a team wants a narrower setup, collection can be restricted. If a project or environment should no longer be included, access can be removed. AgentPM should only collect from places users have approved.

For privacy details, see the privacy policy.

Every organization has different needs.

Some teams want broad visibility across agent-assisted work. Others want collection limited to a specific server, repo, project folder, or rollout group. The right setup depends on how your team works, what systems agents touch, and what boundaries you want in place.

If you are evaluating AgentPM, contact us and we can walk through the collection model that fits your organization.