When you ask Starko AI to fix something on a ticket, it needs to know which codebase to open. That used to fail silently when nothing was configured. Now every ticket can resolve its repository — and asks you when it can't.
Link a repository to a project
Project properties get a Repository field. Operators pick from the repos your GitHub connection can access; members see it as a read-only label. Once set, every ticket in that project dispatches Starko AI into the right repo automatically.
Sensible resolution, visible failures
When you mention @starko, the repo is resolved in order: the ticket's previous run, an explicit pick, the project's linked repo, then the workspace default. If a run still can't start, the AI posts a clear "Starko AI can't start" comment on the ticket instead of failing quietly in the background.
Ad-hoc tickets ask at send time
On a ticket with no resolvable repo, mentioning Starko AI opens a repository picker before your comment sends. Pick one and the run starts with it; cancel and your draft goes right back into the editor.
The "Fix with Starko AI" button now simply inserts the mention into the composer for you, so there's one consistent way to start the AI — the mention. Live for all workspaces with a GitHub connection.