Connector usage examples
The four connector commands all work the same way: type the command, type part of what you are looking for, pick a result, then say what you want done with it. The examples below show that same shape across each provider.
Gmail: turning a bug report into a fix
> /gmail checkout error (dropdown shows matching subjects live) > Tab to pick "Checkout throwing 500 on mobile Safari" > reproduce this and fix it
tCode reads the full email content, resolved server-side from the reference you attached, alongside whatever it finds by reading the actual checkout code, rather than you retyping the report by hand.
Notion: implementing a documented design
> /notion rate limiting design
> Tab to pick "API Rate Limiting: Design Doc"
> implement the token bucket approach described here
This only reaches pages that have already been shared with your tAI connection in Notion; a page that has not been shared will not appear in the results, since tCode cannot resolve content it does not have permission to see.
GitHub: working across a repository you do not have open
> /github payments-service
> Tab to pick "acme-corp/payments-service"
> find where webhook signatures are verified and add logging when one fails
Referencing a repository this way is most useful when the work spans a project other than the one you happen to be sitting in locally.
Linear: implementing straight from a ticket
> /linear timeout on export
> Tab to pick "ENG-482: Large CSV exports time out"
> implement this
The issue's actual description and acceptance criteria come across with the reference, so "implement this" is working from the same specification your team already wrote, not a paraphrase of it.
In every example above, typing a query and pressing Enter without ever opening the dropdown falls back to a plain numbered list instead, useful over a slow connection or when you already know exactly which result you want without watching it filter live.
Combining a connector with a broader request
> /linear login flow
> Tab to pick "ENG-510: OAuth callback fails for expired sessions"
> before fixing this, check if there is a related open issue about session refresh and mention it in the fix's commit message
An attached reference is just additional context for the turn, not the entire scope of it; a prompt can still ask tCode to do further investigation, cross-reference other issues, check related code, on top of whatever the connector reference itself provided.
Using the shared alias instead of a provider-specific command
> /connectors notion onboarding checklist
> Tab to pick "New Engineer Onboarding"
/connectors <provider> <query> behaves identically to typing /notion directly; it exists for the case where typing the general form is more natural than remembering which of the four provider-specific command names to reach for.
Checking what is linked before searching
> /connectors Connectors: /gmail connected /notion connected /github not connected /linear connected
Running /connectors with nothing after it is a quick way to confirm a provider is actually linked before typing out a search, useful right after setting up a new machine or a new tAI account where you are not yet sure what has been connected.
Every example on this page attaches exactly one item to the next message. There is currently no way to attach more than one connector reference to a single message at once; a task that genuinely needs information from two different sources is better handled as two separate turns, attaching and discussing one, then attaching and discussing the other.