Owner

1 indexed repository · View on GitHub

Issues somebody may already be working on are listed last. List everything by date

  • Recheck webhook repeat and hourly policy when admitting a run
    Open
    code-review secondshift

    Difficulty 4/5 3-5 days Newbie friendliness 46/100

    piotrekno1/second-shift#421 ·

    Maintainers usually reply within 1 day

  • Retry repository autosync after a linked skill fetch recovers
    Open
    code-review secondshift

    Difficulty 4/5 3-5 days Newbie friendliness 56/100

    piotrekno1/second-shift#420 ·

    Maintainers usually reply within 1 day

  • Refresh repository jobs when a background sync finishes between dashboard polls
    Open
    code-review secondshift

    Difficulty 2/5 1-3 hours Newbie friendliness 84/100

    piotrekno1/second-shift#419 ·

    Maintainers usually reply within 1 day

  • Surface upstream interruption when a model gateway stream is truncated
    Open
    code-review secondshift

    Difficulty 4/5 3-5 days Newbie friendliness 56/100

    piotrekno1/second-shift#395 ·

    Maintainers usually reply within 1 day

  • Commit gateway usage records and token-budget updates atomically
    Open
    code-review secondshift

    Difficulty 3/5 1-2 days Newbie friendliness 70/100

    piotrekno1/second-shift#394 ·

    Maintainers usually reply within 1 day

  • Preserve completed run reports when runner shutdown fails
    May be free again A pull request for this issue was closed without being merged. Open
    code-review needs-design secondshift

    Difficulty 4/5 3-5 days Newbie friendliness 57/100

    piotrekno1/second-shift#381 · 1 comment ·

    Maintainers usually reply within 1 day

  • Recover delivery retries whose DBOS workflows terminate early
    May be free again A pull request for this issue was closed without being merged. Open
    code-review secondshift

    Difficulty 4/5 3-5 days Newbie friendliness 58/100

    piotrekno1/second-shift#380 ·

    Maintainers usually reply within 1 day

  • Benchmark token use by source before compressing tool output
    Open

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#366 ·

    Maintainers usually reply within 1 day

  • Queue runs that share an agent login instead of failing them
    Open

    Difficulty 4/5 3-5 days Newbie friendliness 57/100

    piotrekno1/second-shift#361 ·

    Maintainers usually reply within 1 day

  • Report what happened to each agent container on the run
    Open

    Difficulty 4/5 3-5 days Newbie friendliness 55/100

    piotrekno1/second-shift#351 ·

    Maintainers usually reply within 1 day

  • Let owners give runs more git history
    Open

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#334 ·

    Maintainers usually reply within 1 day

  • Pin linked skills in a .secondshift.lock file
    Open

    Difficulty 5/5 Over a week Newbie friendliness 12/100

    piotrekno1/second-shift#329 · 1 comment ·

    Maintainers usually reply within 1 day

  • Find SecondShift's own issues by stored number, not by title
    Open

    Difficulty 3/5 Half a day Newbie friendliness 45/100

    piotrekno1/second-shift#311 ·

    Maintainers usually reply within 1 day

  • Check in the production e2e test that deleting a run deletes its artifacts
    Open
    area: deployment

    Difficulty 2/5 1-3 hours Newbie friendliness 72/100

    piotrekno1/second-shift#310 ·

    Maintainers usually reply within 1 day

  • Let Codex runs start sub-agents
    Open

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    piotrekno1/second-shift#260 ·

    Maintainers usually reply within 1 day

  • Delete a job removed from the manifest if it never ran
    Open
    enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 48/100

    piotrekno1/second-shift#245 ·

    Maintainers usually reply within 1 day

  • Hide jobs removed from the manifest by default
    Open
    area: dashboard enhancement

    Difficulty 3/5 1-2 days Newbie friendliness 57/100

    piotrekno1/second-shift#244 ·

    Maintainers usually reply within 1 day

  • Hold a subscription's runs until its usage allowance resets
    Open

    Difficulty 5/5 Over a week Newbie friendliness 30/100

    piotrekno1/second-shift#200 ·

    Maintainers usually reply within 1 day

  • Queue a trigger request that arrives during an active run
    Open
    area: runs enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 22/100

    piotrekno1/second-shift#163 ·

    Maintainers usually reply within 1 day

  • Cost estimate before a run
    Open
    area: dashboard area: runs enhancement idea

    Difficulty 3/5 1-2 days Newbie friendliness 42/100

    piotrekno1/second-shift#156 ·

    Maintainers usually reply within 1 day

  • Start jobs from GitHub events
    Open
    area: runs idea

    Difficulty 4/5 3-5 days Newbie friendliness 22/100

    piotrekno1/second-shift#150 ·

    Maintainers usually reply within 1 day

  • Audit log for access decisions and connection settings
    Open
    area: access

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    piotrekno1/second-shift#142 ·

    Maintainers usually reply within 1 day

  • Per-job memory and CPU limits
    Open
    area: runner

    Difficulty 4/5 3-5 days Newbie friendliness 40/100

    piotrekno1/second-shift#137 ·

    Maintainers usually reply within 1 day

  • Built-in CircleCI connector for CI logs
    Open
    area: connectors help wanted idea

    Difficulty 4/5 3-5 days Newbie friendliness 54/100

    piotrekno1/second-shift#113 ·

    Maintainers usually reply within 1 day

  • Built-in Buildkite connector for CI logs
    Open
    area: connectors help wanted idea

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#112 ·

    Maintainers usually reply within 1 day

  • Monthly spend cap per workspace and job
    Open
    area: dashboard area: runs enhancement

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#83 · 1 comment ·

    Maintainers usually reply within 1 day

  • Built-in WildEdge.dev connector
    Open
    area: connectors help wanted idea

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#63 ·

    Maintainers usually reply within 1 day

  • External credential managers (1Password, HashiCorp Vault)
    Open
    area: auth idea

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#60 ·

    Maintainers usually reply within 1 day

  • Single sign-on (OIDC, Okta, Google Workspace)
    Open
    area: auth idea

    Difficulty 5/5 Over a week Newbie friendliness 30/100

    piotrekno1/second-shift#59 · 1 comment ·

    Maintainers usually reply within 1 day

  • Identity sources for quarterly-access-review (Okta, Google Workspace, AWS IAM)
    Open
    area: connectors idea

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#56 ·

    Maintainers usually reply within 1 day

  • Notion and Confluence connectors for docs-drift
    Open
    area: connectors idea

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#55 ·

    Maintainers usually reply within 1 day

  • Built-in Datadog connector (and Grafana, Prometheus)
    Open
    area: connectors help wanted idea

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#53 · 1 comment ·

    Maintainers usually reply within 1 day

  • Built-in PagerDuty connector (and Opsgenie, incident.io)
    Open
    area: connectors help wanted idea

    Difficulty 5/5 Over a week Newbie friendliness 45/100

    piotrekno1/second-shift#52 ·

    Maintainers usually reply within 1 day

  • Built-in Linear and Jira connectors
    Open
    area: connectors idea

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#51 ·

    Maintainers usually reply within 1 day

  • Email digests of run reports
    Open
    area: delivery idea

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#50 ·

    Maintainers usually reply within 1 day

  • Microsoft Teams delivery
    Open
    area: delivery help wanted idea

    Difficulty 4/5 3-5 days Newbie friendliness 48/100

    piotrekno1/second-shift#48 ·

    Maintainers usually reply within 1 day

  • Native Slack app with run actions
    Open
    area: delivery idea

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    piotrekno1/second-shift#47 ·

    Maintainers usually reply within 1 day

  • Human-approved actions: jobs propose, people approve, the broker writes
    Open
    area: access idea

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#46 ·

    Maintainers usually reply within 1 day

  • Idea: Track recurring findings across runs through resolution
    Open
    area: runs idea

    Difficulty 5/5 Over a week Newbie friendliness 30/100

    piotrekno1/second-shift#11 · 1 comment ·

    Maintainers usually reply within 1 day

  • Add pi agent backend support
    Open
    area: agents enhancement

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    piotrekno1/second-shift#10 ·

    Maintainers usually reply within 1 day

  • Support controlled outbound access from sandboxes
    Open
    area: runner enhancement

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    piotrekno1/second-shift#3 ·

    Maintainers usually reply within 1 day

  • Fix failed-delivery retries on PostgreSQL
    Possibly taken @piotrekno1 claimed this today. Open
    code-review fix-approved secondshift

    Difficulty 3/5 1-2 days Newbie friendliness 35/100

    piotrekno1/second-shift#418 ·

    Maintainers usually reply within 1 day

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.