Get it for macOS

Bring all your Korey connectors into your coding conversations in bb. Research across connected services and create or update Shortcut Stories. Continue the same private Korey conversation across coding harnesses and attach workspace files. Requires a Korey account, a personal access token, and configured connectors.


Overview

View source

Your Korey connectors, in bb

Use any connector available in your Korey workspace from your coding conversations in bb. Give Korey the outcome and relevant context; it works with your connected services using your workspace's conventions.

For example, ask Korey to summarize Sentry errors, explain LaunchDarkly flags, or compare an implementation plan with existing Shortcut Stories. These are examples, not an exhaustive list of the connectors you can use.

When you ask to create or update a Shortcut Story, Korey handles the request through its Shortcut connector using your workspace's conventions.

Keep the conversation going

Each bb thread can continue a linked private Korey conversation, including when you switch coding harnesses. Attach up to five supported workspace files to add context, or link an existing private Korey conversation.

Get started

  1. Connect your services in Korey. Connector setup and reauthentication stay in Korey.
  2. Create a personal access token with threads:read and threads:write scopes.
  3. Add the token under Settings → Installed plugins → Korey in bb.
  4. Start a request with “Ask Korey…” or use bb korey ask from the CLI.

Requires a Korey account and access to the relevant connected services. Available data and actions depend on your Korey workspace's connectors and permissions.

See the connector guides and plugin documentation for more details.

More from Shortcut

Agent CalendarSee what your agents worked on and when, as a calendar of work blocks or a weekly time sheet. Each thread gets a block for the time its agent turns ran, colored by project, in a day, 3-day, or week view. Switch to Projects to merge a project's parallel threads into one entry, or open the time sheet to copy hours per thread and day as CSV. Agents can answer "what did my agents work on last week?" with the bb agent-calendar command and its bundled skill. Turn history stays in a local database on the bb server and uses no external service.215Agent TracesSee where your agents' time goes, from every thread down to each command, tool call, and subagent of a turn. A turn opens as a timeline that splits the agent's time into waiting on you, tools, subagents, thinking, writing, and model time, and it grows live while the agent works. Select a call to see its exit code, output, and arguments, or jump to the reply that followed it in the chat. A Traces page in the sidebar compares your recent threads by active time, calls, and errors, and two turns can be compared phase by phase. Turns export as OpenTelemetry or an HTML snapshot, and the bb agent-traces command gives agents the same answers. Traces come from the thread history on your bb server; an OpenTelemetry collector is optional.277DependabotReviews GitHub Dependabot alerts grouped by dependency and sends grouped fixes to BB agents.18Disk UsageShows what's taking up disk space on the bb server host, ncdu-style, with drill-down by directory and a bb disk-usage CLI.63

More in Tasks & Workflows 66

Plan, track, route, schedule, or automate work.

View all