Issues

The Issues page is a unified, cross-repository view of every issue flowcy.dev has seen. Issues are synced from GitHub webhooks the moment they're opened, edited, closed, or reopened — there's no need to import anything manually.

What you can do here

• Filter by state — open or closed.
• Paginate through history with cursor-based navigation.
• Click into an issue to see its title, body, labels, assignees, and the AI agent's reasoning if it touched the issue.

How issues end up here

The moment you install the GitHub App on a repository, flowcy.dev starts receiving issues webhook events. For each event it stores:

• The issue metadata (title, body, state, labels, etc.).
• A vector embedding of the title + body, used for PR-to-Issue linking and semantic search.

Embeddings are generated by the AI agent and stored in Turso's built-in vector index. This is what makes it possible for a new pull request to be automatically linked to a related issue from months ago.

Automations that touch issues

If you've left the defaults on, every new issue gets:

1. Issue labeling — the agent reads the title + body and applies the most relevant labels from the repository's existing label set.
2. Project linking — the issue is added to the first GitHub Project (v2) attached to the repo.
3. Sub-issue suggestions — for complex issues, the agent may propose a breakdown into smaller sub-issues.

All three are toggleable in Settings → Automation.