Add pi agent backend support
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- ai-infra-agents, backend
Research direction
Start by reading issue #7 for the shared backend contract, then confirm pi’s upstream identity and supported integration surface before choosing dependencies. Trace how scheduled skills, pinned repository snapshots, and run records are handled in the existing backend. Done means an end-to-end pi smoke test stores a report, the listed security and lifecycle tests pass, and setup instructions explain supported environments and limits.
Written by the indexing model from the issue text.
Description
Add pi as a native agent backend for scheduled repository skills.
Depends on #7, which defines the shared backend contract. Use that contract rather than introducing a separate execution and security model.
Scope
- Execute a selected committed skill against the pinned repository snapshot.
- Use a server-owned configuration for the supported agent version, model, and authentication method.
- Preserve approved capability boundaries and keep credentials outside command sandboxes.
- Map progress, tool evidence, reports, usage, failures, and cancellation to SecondShift run records.
- Enforce effective run budgets and document any backend-specific limits.
- Document supported operating environments and installation requirements.
Acceptance criteria
- An end-to-end smoke test completes a scheduled skill and stores its report using pi.
- Tests cover denied tool access, credential isolation, timeout, cancellation, and cleanup.
- Repository input cannot select arbitrary executables, runtime flags, mounts, or credentials.
- Unsupported security requirements fail before execution rather than silently falling back.
- Usage reporting clearly identifies values the backend cannot provide.
- Setup instructions include a working example and explain supported authentication and deployment constraints.
Confirm the upstream project identity and supported integration surface during implementation before choosing dependencies.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 322
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from piotrekno1/second-shift
-
code-review secondshift
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
piotrekno1/second-shift#419 ·
Maintainers usually reply within 1 day
-
area: deployment
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
piotrekno1/second-shift#310 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 46/100
piotrekno1/second-shift#421 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 56/100
piotrekno1/second-shift#420 ·
Maintainers usually reply within 1 day
-
Fix failed-delivery retries on PostgreSQLPossibly taken @piotrekno1 claimed this today. Opencode-review fix-approved secondshift
Difficulty 3/5 1-2 days Newbie friendliness 35/100
piotrekno1/second-shift#418 ·
Maintainers usually reply within 1 day
All issues in piotrekno1/second-shift
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day