Issue sync

Issue sync gives the loop a queue that humans already manage: your tracker. Issues labeled with a chosen label become tasks; status comments and PR links flow back to the issue.

Configure a source

openloop issue set-source -p api \
  --github myorg/myrepo \
  --label openloop \
  --token "$GITHUB_TOKEN" \
  --auto-sync

• --github owner/name or --gitlab group/name, exactly one.
• --label, only issues with this label are imported (default openloop).
• --token, GitHub PAT (sent as Bearer) or GitLab token (sent as PRIVATE-TOKEN). Stored in project.json; you can also pass it per-sync instead.
• --auto-sync, sync every 30 minutes during daemon ticks.
• --post-comments, post status updates back to issues (default on).

Sync and inspect

openloop issue sync -p api            # manual sync (optionally --token …)
openloop issue list -p api            # what's been imported

#    title                                        state   taskId
142  Rate-limit /login attempts                   open    rate-limit-login-attempts
156  Migrate auth library to v3                   open    migrate-auth-lib

Each imported issue becomes a proposed task whose source points at the issue; the id/URL shows up in task show.

What flows back

With --post-comments on, OpenLoop comments on the issue when:

• the task starts running,
• a promotion is queued (with the PR link, when one is created).

So a maintainer watching the issue sees the loop’s progress without opening OpenLoop at all.

Removing a source

openloop issue remove-source -p api

Stops future syncs; already-imported tasks stay in the ledger.