ceven

Sourcegraph

Indexes your entire codebase to automate dependency audits, generate pull request summaries, and track technical debt across every repository.

Try Sourcegraph in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Sourcegraph integration

    • Describe the outcome and Ceven picks the right Sourcegraph calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Sourcegraph data, across all 8 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Sourcegraph access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Sourcegraph, when, and on whose behalf.
    • The agent pauses and asks when Sourcegraph is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Sourcegraph.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Sourcegraph action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Sourcegraph, and when to use it.

Compare Commits
Use this when you need to retrieve file diffs between two specific commit shas to analyze changes.
Get Commit Details
Pull detailed metadata and author information for a specific commit in a repository.
Get Current User
Retrieve the identity and permissions of the authenticated user for API verification.
Get File Contents
Fetch raw text from a specific file on the default branch without cloning the repository.
List Repositories
Pull a paginated list of all repositories available on the Sourcegraph instance.
List Repository Files
Enumerate all files and directories within a specific repository path.
List Repository Languages
Determine the primary and secondary languages used in a given repository.
Check Site Settings Permission
Confirm if the API allows site settings edits before attempting configuration changes.
Check Site Settings Edit Permission
Tool 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.

9 actions · scroll to see them all

Frequently asked questions

Ceven operates using the permissions of the authenticated user token provided during connection. If the user does not have read access to a specific private repository within Sourcegraph, the agent will be unable to pull file contents or list files for that repo. We do not bypass any access control lists or organizational policies set within your Sourcegraph instance. This ensures that your internal security boundaries remain intact while the agent automates workflows. If a workflow fails due to a permission error, the agent will notify you that the connected account lacks the necessary scopes to access that specific code asset.
Ceven uses Sourcegraph for intelligence and discovery, but it does not write directly to your git provider through the Sourcegraph API. Instead, the agent uses Sourcegraph to find the exact lines of code and files that need changing, then it uses your connected GitHub or GitLab integration to create the actual pull requests. This separation ensures that you have a full audit trail of changes in your version control system. The agent identifies the target via Sourcegraph and executes the change via the git provider, giving you the best of both worlds for discovery and deployment.
Ceven respects the rate limits imposed by your Sourcegraph tier. For cloud users, this is typically managed via a token bucket algorithm. If the agent hits a rate limit during a large scale search, it will automatically enter a backoff and retry loop to avoid being throttled further. One specific quirk is that complex GraphQL queries with deep nesting can be more expensive than simple REST calls. If you notice slow performance on massive repositories, the agent will attempt to break the request into smaller paginated chunks to stay within the operational limits of your instance.
No. Ceven does not clone your repositories or store your source code on its own disks. It treats Sourcegraph as a remote index. When a workflow needs to analyze a file, the agent fetches the content into volatile memory, processes the necessary logic, and then discards the data. We only store the metadata required to maintain the connection and the logs of the actions taken. Your intellectual property stays within your Sourcegraph instance and your git provider, ensuring that no permanent copies of your codebase exist outside your controlled environment.
Yes. You can create workflows that search for specific patterns, such as TODO comments or deprecated function calls, across all your repositories. The agent can then aggregate these findings into a report or create a backlog in your project management tool. By combining Sourcegraph search with Ceven logic, you can prioritize debt based on how often a piece of code is actually changed or referenced. This turns a static search result into an actionable plan for your engineering team to improve code quality over time.
The agent uses the Sourcegraph API to request a diff between two specific commit shas. It retrieves the changes at the file level, identifying exactly which lines were added or removed. This is particularly useful for generating automated changelogs or auditing a specific bug introduction. The agent can then summarize these technical diffs into human readable language for stakeholders. Because it uses the Sourcegraph index, this process is significantly faster than manually checking out two different branches in a local environment and running a git diff command.
Yes, provided that your on premise instance is reachable by Ceven. You will need to ensure that your firewall allows incoming requests from our IP range and that you have a valid API token. For highly restricted environments, we recommend using a proxy or a secure tunnel. The API surface is consistent between the cloud and on premise versions, so all actions like listing repositories or fetching file contents will work identically. Just ensure your admin has enabled the necessary API permissions for the account you use to connect.

Alternatives to Sourcegraph

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

GitHub logoGitHubGitLab logoGitLabBitbucket logoBitbucket

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Sourcegraph and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free