Skip to content

Add Prime Agent support for Pi integration - #822

Closed
samsja wants to merge 1 commit into
herdrdev:masterfrom
samsja:feat/prime-agent-support
Closed

Add Prime Agent support for Pi integration#822
samsja wants to merge 1 commit into
herdrdev:masterfrom
samsja:feat/prime-agent-support

Conversation

@samsja

@samsja samsja commented Jun 26, 2026

Copy link
Copy Markdown

No description provided.

Prime Agent (formerly Pi) renamed its config directory from
~/.pi/agent to ~/.prime/agent and its env var from
PI_CODING_AGENT_DIR to PRIME_AGENT_CODING_AGENT_DIR.

Changes:
- env.rs: pi_extension_dir() checks PRIME_AGENT_CODING_AGENT_DIR
  first, then PI_CODING_AGENT_DIR, then prefers ~/.prime/agent
  when it exists, falling back to ~/.pi/agent for legacy installs
- env.rs: omp_extension_dir() also checks both env vars
- env.rs: add config_dir_from_envs_or_home and config_dir_from_env
  helpers
- targets.rs: install_pi() now creates the extensions directory if
  the agent directory already exists (matching install_omp behavior)
- registry.rs: add 'prime-agent' as a detected command name for Pi
- detect/mod.rs: identify_agent and parse_agent_label now recognize
  'prime-agent' as Agent::Pi
- Tests for all new paths and behaviors
- Documentation updates for Pi / Prime Agent

The extension code itself (herdr-agent-state.ts) already works with
Prime Agent's extension API without changes - only the discovery and
installation paths needed updating.
@kangal-bot

Copy link
Copy Markdown
Collaborator

Hi @samsja, thanks for your interest in contributing!

New contributors need maintainer approval before opening PRs. This keeps review time focused on accepted work and avoids wasted effort.

Herdr is opinionated about how it should look, feel, and work. Feature requests, ideas, questions, contribution proposals, and product-direction checks belong in Discussions, not issues.

Next steps:

  1. If this is a feature or behavior change, open a Discussion describing what you want to change and why
  2. If the work is accepted, a maintainer may convert the discussion into an issue or create a new issue for it
  3. If this is a reproducible bug, open a bug report using the issue template
  4. Wait for maintainer approval on an accepted issue before opening a PR
    Maintainers approve first-time PR paths with /approve @your-github-username on the accepted issue.
  5. Keep it concise and write in your own voice

A discussion, issue, branch, or proposed implementation does not reserve the work and does not mean the PR path is approved.

This PR will be closed automatically. See https://github.com/ogulcancelik/herdr/blob/master/CONTRIBUTING.md for more details.

@kangal-bot kangal-bot closed this Jun 26, 2026
@samsja
samsja deleted the feat/prime-agent-support branch June 26, 2026 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants