Sanaf AI
Start free
Developer Tools

Sourcegraph, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Sourcegraph account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Connects with a key
  • 8 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Sourcegraph is

Sourcegraph is a code intelligence platform that enables developers to search, understand, and manage code across large codebases.

You paste in a key from your own Sourcegraph account. It is kept encrypted, and you can withdraw it from inside Sourcegraph whenever you like.

How a run works

One message in, the work done in Sourcegraph.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Sourcegraph. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Sourcegraph account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

8 tools it already has

What it can do in Sourcegraph

These are the ready-made tools your AI employee already has in Sourcegraph. It is not limited to them, but it never has to be taught these.

  • Check Site Settings Edit PermissionTool to check whether site settings can be edited through the api. use when you need to confirm the api allows site settings edits before attempting configuration changes.
  • Compare CommitsTool to compare two commits in a repository and retrieve their file diffs. use after confirming the repository name and commit shas to inspect differences.
  • Get Commit DetailsGet detailed information about a specific commit in a repository.
  • Get Current UserTool to retrieve information about the currently authenticated user. use when needing confirmation of identity via sourcegraph graphql api.
  • Get File ContentsTool to fetch the contents of a specified file on the default branch. use when you need raw file text without cloning the repo or using a slower code-host api.
  • List RepositoriesTool to list repositories on the sourcegraph instance. use when you need to paginate through all available repositories.
  • List Repository FilesTool to list all files and directories in a repository path. use when you need to enumerate files in a repository without cloning.
  • List repository languagesTool to list languages used in a repository. use when you need to determine the primary and all languages of a given repository; call after you have the repository name.
Access, and who is in charge of it

You stay the boss of your Sourcegraph account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Sourcegraph account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Sourcegraph is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Sourcegraph and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Sourcegraph

Can an AI employee really work inside Sourcegraph?
Yes. It signs in to your own Sourcegraph account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Sourcegraph?
No. Nothing moves and nothing is replaced. Your records stay in Sourcegraph, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Sourcegraph account?
You paste in a key from your own Sourcegraph account. It is kept encrypted, and you can withdraw it from inside Sourcegraph whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Sourcegraph?
It has 8 ready-made tools in Sourcegraph today, among them Check Site Settings Edit Permission, Compare Commits and Get Commit Details. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Sourcegraph and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Sourcegraph and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Sourcegraph?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Sourcegraph is written down with what it did and when.