Support

How to reach us

Most answers are below. If yours is not, write to us at the bottom of the page. Slack community access is not open yet.

Before you write in

  • Status says whether something is down for everyone rather than just for you.
  • The docs cover session start, writing entries, rules, watchers, digests and export.

Questions people ask

Getting started

Your agent connected, but it found nothing to read
This workspace is probably watching no repositories yet, so the record really is empty — there is nothing wrong with the connection. Connect one in Repositories. That is an admin action, so if you are not an admin, ask one of them to do it and then run your agent again.
Your agent does not see the scout_ tools
Restart the session. A server added part-way through one is not loaded until the agent starts again, and reconnecting is not enough. If it works in one project but not another, the server was added for that project only — adding it with --scope user registers it everywhere.
You no longer have a key you created
Scout shows a key once, at the moment it is created, and cannot show it again — not on Setup and not on Agents & keys. Create another named key from either of those pages, or replace the one you lost. A new named key does not revoke the others. Replace revokes only the key you chose, in the same transaction, so anything still using that key stops working: save the new secret as SCOUT_API_KEY where that one was.
A key you were already using stopped working
A new named key does not revoke the others. Replace does, for the one key you chose, and it happens in the same transaction — another machine, CI, or an agent still using that key stops at that moment. Your other keys keep working. Save the new secret as SCOUT_API_KEY where the replaced one was.
Your agent says Scout refused it as unauthorized
Your tool is not sending a working key, or it is not signed in. The key-based steps on Setup read SCOUT_API_KEY, set to the secret of the named key you picked, so check that variable is set where the tool runs: open a new terminal after saving it, then restart the tool. Claude Desktop cannot read it from your shell at all — its config needs the key written in where it says <YOUR_API_KEY>, or add Scout as a custom connector and sign in through the browser instead. If you replaced a key, the variable may still hold the old secret. A new named key does not revoke the others.

Connecting repositories

How do I connect a GitHub organization?
Open Connections in your workspace and choose Connect a GitHub organization. If Scout asks you to authorize it on GitHub first, do that. GitHub then asks which account to install Scout on: choose the organization, pick the repositories Scout may read, and you come back to Scout. A workspace can hold many GitHub organizations. After one is connected, choose Connect a GitHub organization again. The section is headed Add another GitHub organization or Bitbucket workspace, or Add another GitHub organization once Bitbucket is already connected. A GitHub organization can belong to one Scout organization at a time.
My organization is not listed
When Connections shows Ready to connect, that list is only organizations where Scout is already installed, that this workspace does not hold, and that no other Scout workspace holds. A row there offers Connect this organization. An organization this workspace already holds is already connected, so it is not under Ready to connect. Connections does not list every organization you can see on GitHub. For one that is not in that list, choose Connect a GitHub organization. An organization that another workspace in your Scout organization holds is not under Ready to connect either: open Connections and choose Choose repositories, where it is listed as connected to another workspace, and pick its repositories. Organizations another Scout organization already holds are kept closed. The closed line tells you how many of your GitHub organizations are connected in other Scout organizations. When there is one, it says one of your GitHub organizations is connected in another Scout organization. Open the count to see the organization names. When Scout names the workspace that holds one, you see that name only when you belong to that workspace; otherwise you see the organization and not the workspace. A GitHub organization can belong to one Scout organization at a time. To connect it to this workspace instead, disconnect it in the other Scout organization first.
GitHub asked for approval and nothing connected
GitHub can turn an install into a request for approval, so nothing is connected yet. Nothing went wrong, and trying again will only repeat the request. It needs a GitHub organization owner to approve Scout on GitHub.
Can I connect Bitbucket?
Yes, Bitbucket Cloud. Only a Bitbucket workspace owner can grant it, because Scout creates a webhook on the workspace. Another workspace in the organization can join that connection without signing in to Bitbucket: open Connections and choose Choose repositories, then pick the repositories that workspace watches.

API keys & agents

I think my API key has leaked
Create a new key from your workspace's API keys page. Creating one revokes the key it replaces, so the leaked one stops working. If you write to us about it, send the key's first few characters only, never the whole key.

Billing

How is a seat defined?
A seat is a human developer — somebody with a login. Their agents, IDEs, machines and watchers connect under that seat and are never billed. We bill the human.
Do you offer annual billing?
Yes. Annual: two months free. Same Team plan.
What constitutes an early-stage startup?
Under $1M raised or under $250K annual revenue. We review every application by hand to keep the program pointed at the teams it is for. Apply to find out.
Can we self-host Scout?
Not today. Scout is a managed service, so a session starts with no setup. Custom deployment is on the roadmap and we are not putting a date on it. Export is always available, in the same file layout the open-source tool uses. Nothing is trapped.
What happens on day 15?
Billing starts. The card you added is charged for the developers on the workspace that day. If the charge fails we retry for ten days, and after that writing is paused — everything you have written stays and stays readable, and export is always available.
Is there a free plan?
No. There is a free trial and a startup program. A free plan is how you end up with a product for people who will never pay for it.
How do I cancel?
An admin opens Manage billing on the workspace's Billing page. That opens Stripe's billing portal, where the subscription can be canceled.

Account

How do I link GitHub or Bitbucket to my account?
Open Account settings and connect the provider you want. It attaches that identity to the account you are signed in with.

Still stuck? Write to us

What to include

Four things usually save a round trip:

  • Your workspace slug — it is in the URL, as in /your-team/dashboard.
  • Which agent or MCP client you were using.
  • What you expected, and what happened instead.
  • Roughly when it happened, with a timezone.

Please do not send us an API key. If you think one has leaked, replace it from your workspace's API keys page and tell us the prefix only.

Email support@cascadeaipartners.com.

Slack

Community invite is not available yet.