Provelypi connects to Provely through the CLI, the REST API. The agent does the action. Provely verifies the outcome and signs a receipt. pi never holds the verifier credentials.
A person verified the pi capabilities on 2026-09-08. Agent products change monthly. Re-verify before you build.
Source: integration profile pi · retrieved 2026-09-08
Which surfaces does pi use?
| Surface | Support | Detail |
|---|---|---|
| MCP server | Not supported | transport |
| CLI | Supported | Runs through the shell tool of the agent. |
| SDK | Not supported | |
| REST API | Supported | Any HTTP call reaches the control plane. |
Which guidance files does pi read?
Provely ships one Agent Skill for this host, so the agent knows to verify an outcome before it claims done. The renderer writes AGENTS.md fragment, Agent Skills SKILL.md from one source. A new agent needs a profile, not core code.
Explain: each file, its path and its write mode
| Format | Path | Mode |
|---|---|---|
| AGENTS.md fragment | AGENTS.md | append |
| Agent Skills SKILL.md | .pi/skills/provely-outcome-verification/SKILL.md | write |
| CI gate workflow | .provely/ci/github-actions.yml | fragment |
How is a false completion claim blocked?
Guidance asks. A hook and the CI gate enforce. A host with neither still receives the verdict, and a person reads it before the work ships.
Explain: what each control does on this host
| Enforcement | Support | Detail |
|---|---|---|
| Advisory guidance | Supported | The instruction files state the rules for every agent. |
| Lifecycle hooks | Verify at implementation | No hook events stated. |
| CI gate | Supported | provely verify --wait fails the pipeline unless the verdict is VERIFIED. |
How do I connect pi?
Connect pi to Provely
- Install the CLI.Run
curl -fsSL https://provely.sh/install.sh | sh. On Windows, runirm https://provely.sh/install.ps1 | iex. Each script verifies the signed checksum before it installs the binary. - Write the guidance files.Run
provely init --agent pi. It writesAGENTS.md(append),.pi/skills/provely-outcome-verification/SKILL.md(write),.provely/ci/github-actions.yml(fragment). The guidance carries one rule: a successful tool call is not completion. - Add the CI gate.Run
provely verify --wait <duration>in the pipeline. The step fails unless the verdict is VERIFIED. Exit codes: 0 VERIFIED, 2 PENDING, 3 FAILED, 4 CONTRADICTED, 5 UNVERIFIABLE, 1 error. - Report the verdict exactly as returned.VERIFIED: "The action is verified complete. Receipt: <id>." PENDING: "The action is accepted but not yet verified. Operation: <id>."
What else does the profile state?
- Verified 2026-09-08: pi reads ~/.pi/agent/AGENTS.md, then AGENTS.md or CLAUDE.md from the parent directories and the working directory. AGENTS.override.md of a directory replaces both. Source: https://github.com/earendil-works/pi (docs/quickstart.md).
- Verified 2026-09-08: pi reads skills from ~/.pi/agent/skills, ~/.agents/skills, .pi/skills, and .agents/skills. A project skill needs trust. Source: docs/skills.md of the same repository.
- Verified 2026-09-08: pi has no built-in MCP. The README states "No MCP". Only a third-party extension adds MCP, so this profile names no MCP transport and no remote auth shape.
- Verified 2026-09-08: a pi extension registers pi.on("tool_call") and returns { block: true, reason } to block a call before it runs. Source: docs/extensions.md. We ship no pi extension, so hooks stay verify_at_implementation and the rendered files state that they are advisory.
- The source repository moved from badlogic/pi-mono to earendil-works/pi. The author is the same. The CLI surface works through the pi tool execution.
pi keeps its action credentials, and no surface returns the verifier credentials to it. Read the credential boundary. An operation outlives the session that opened it. Read the API reference.
Which host versions does the profile cover?
>=0.80.0. The integrations team last verified the profile with 0.85.1 of 2026-09-05 on 2026-09-08 (npm @earendil-works/pi-coding-agent).