You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MANUAL RUN: codeSplitters: check the dig panel's agent GitHub button with real linked GitHubs (#438) #439
#438 added a bot button to each linked-GitHub chip on the dig panel. It chooses which GitHub hosted agents work as (`POST /api/github/agent`). The route and the hosted run are covered by tests, but the button wasn't opened in a browser, because the chips only render with real GitHub sign-ins linked.
To check on the live site, signed in with two GitHubs linked:
The bot button starts dimmed (no account chosen). Clicking it on one account lights that account's button, and clicking it again clears the choice.
Choosing an account for agents doesn't change which account you dig as.
A hosted agent run answers `github: true` once an account is chosen.
Checked on the live site (edd5c23) via #609 with one linked GitHub: the bot button starts as bot-off, lights on click, clears on a second click, and the dig-as ✓ stays put. Not checked: the bot choice on one account while digging as a second (no second GitHub; covered by route tests), and a hosted agent run answering github: true (needs an Anthropic key on the Worker). Leaving open for those.
Checked on the live site via #609 with one linked GitHub: the bot button starts as bot-off, lights on click, clears on a second click, and the dig-as ✓ stays put. Not checkable now: the bot choice on one account while digging as a second (the owner has one GitHub; route tests cover it), and a hosted agent run answering github: true (needs an Anthropic key on the Worker). Closing; reopen if a second GitHub or a hosted key shows up.
Activity
QuinnsCode commentedon Oct 11, 2026
Checked on the live site (edd5c23) via #609 with one linked GitHub: the bot button starts as bot-off, lights on click, clears on a second click, and the dig-as ✓ stays put. Not checked: the bot choice on one account while digging as a second (no second GitHub; covered by route tests), and a hosted agent run answering
github: true(needs an Anthropic key on the Worker). Leaving open for those.QuinnsCode commentedon Oct 11, 2026
Checked on the live site via #609 with one linked GitHub: the bot button starts as bot-off, lights on click, clears on a second click, and the dig-as ✓ stays put. Not checkable now: the bot choice on one account while digging as a second (the owner has one GitHub; route tests cover it), and a hosted agent run answering
github: true(needs an Anthropic key on the Worker). Closing; reopen if a second GitHub or a hosted key shows up.