Add pi agent backend support

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

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

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

area: agents enhancement

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from piotrekno1/second-shift

All issues in piotrekno1/second-shift

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.