Pre-flight checklist
Problem statement
brv connectors install supports 26 agents but has no entry for Pi (pi CLI, published as @earendil-works/pi-coding-agent). Pi is a coding-agent harness with first-class support for the Agent Skills standard, MCP (via extensions), and AGENTS.md-style project instructions — the same integration surfaces ByteRover already targets for other agents. Today, Pi users can't run brv connectors install "Pi" and have no supported path to wire up ByteRover memory.
Proposed solution
Add Pi to the supported-agents table, defaulting to the Agent Skill connector type:
Pi Agent Skill Rules, MCP, Agent Skill
Per-type feasibility (verified against Pi docs v0.80.3):
- Agent Skill (recommended default) — Pi natively implements the Agent Skills standard and discovers
SKILL.md folders recursively from ~/.agents/skills/ and project .agents/skills/ (plus its own ~/.pi/agent/skills/, .pi/skills/). Because .agents/skills/ is the shared cross-harness location, a ByteRover skill written there may already be picked up by Pi with no Pi-specific code. (Source: Pi docs/skills.md, "Locations")
- Rules — Pi reads
AGENTS.md as project instructions; a rules connector can write there.
- MCP — Pi ships no built-in MCP by design (
docs/usage.md: "It intentionally does not include built-in MCP… You can build or install those… as extensions or packages"). An MCP connector would require the user to install a Pi MCP extension first, so it's supported-with-prerequisite rather than out-of-the-box.
Alternatives considered
- Point Pi at another agent's skills dir manually (Pi's settings accept a
skills array of extra paths, e.g. ~/.claude/skills) — works as a workaround but is undiscoverable and not what brv connectors install offers other agents.
- Hand-write a ByteRover rules block into
AGENTS.md — manual, no install/switch/uninstall lifecycle.
Area
Hub / Connectors
Additional context
- Pi skills docs (locations, standard compliance):
docs/skills.md
- Pi "no built-in MCP" note:
docs/usage.md
- Agent Skills standard: https://agentskills.io/specification
- Version tested:
pi 0.80.3
Pre-flight checklist
Problem statement
brv connectors installsupports 26 agents but has no entry for Pi (piCLI, published as@earendil-works/pi-coding-agent). Pi is a coding-agent harness with first-class support for the Agent Skills standard, MCP (via extensions), andAGENTS.md-style project instructions — the same integration surfaces ByteRover already targets for other agents. Today, Pi users can't runbrv connectors install "Pi"and have no supported path to wire up ByteRover memory.Proposed solution
Add Pi to the supported-agents table, defaulting to the Agent Skill connector type:
Per-type feasibility (verified against Pi docs v0.80.3):
SKILL.mdfolders recursively from~/.agents/skills/and project.agents/skills/(plus its own~/.pi/agent/skills/,.pi/skills/). Because.agents/skills/is the shared cross-harness location, a ByteRover skill written there may already be picked up by Pi with no Pi-specific code. (Source: Pidocs/skills.md, "Locations")AGENTS.mdas project instructions; a rules connector can write there.docs/usage.md: "It intentionally does not include built-in MCP… You can build or install those… as extensions or packages"). An MCP connector would require the user to install a Pi MCP extension first, so it's supported-with-prerequisite rather than out-of-the-box.Alternatives considered
skillsarray of extra paths, e.g.~/.claude/skills) — works as a workaround but is undiscoverable and not whatbrv connectors installoffers other agents.AGENTS.md— manual, no install/switch/uninstall lifecycle.Area
Hub / Connectors
Additional context
docs/skills.mddocs/usage.mdpi 0.80.3