Skip to content
Clarobase

Code explainer for engineering teams

Understand and own the code you ship.

Ask how a feature works, hear a spoken walkthrough, and check the answer against the source.

Clarobase DocHub showing documentation for Depot’s public machine-agent repository, with a page sidebar and a Mermaid diagram of the BuildKit cache policy
Clarobase DocHub · depot/machine-agent

Works with the coding assistants your team already uses

  • Cursor
  • GitHub Copilot

Cursor and GitHub Copilot are trademarks of their respective owners. Not affiliated with or endorsed by them.

The real problem

AI writes faster than people can understand it.

Understanding code, not writing it, is now the slow part.

Refactoring is shrinking

In 211 million changed lines, refactoring fell from 25% of changed lines in 2021 to under 10% in 2024, while cloned lines rose from 8.3% to 12.3%.

Correlational. Does not show AI caused it. GitClear 2025

Spend does not add context

DORA describes AI as an amplifier of an organization's existing strengths and weaknesses, not a fix for them.

Qualitative finding. Google DORA 2025

You own what you merge

Developers spent about 58% of their time on program comprehension, in a field study of 78 professionals.

Older study, before AI assistants. Xia et al., 2018

Product

A code explainer, grounded in your documentation.

Hear how your code works, with the knowledge base behind every answer.

Code explainer

Ask how it works. Hear it explained.

Ask by voice or text and hear a spoken walkthrough, with the sources behind the answer so you can check them.

  • Spoken walkthroughs
  • Sources you can check

Knowledge base

The knowledge base that grounds every answer.

Documentation built from your code gives every answer context. How it is built is something we cover with you in a walkthrough.

Connector

Give coding agents the same grounded context.

A connector lets your coding assistants use the same understanding your team does, within team space permissions. Details are shown in a walkthrough.

How it works

From repository to grounded explanation.

  1. Connect your repositories

    You choose which repositories to connect.

  2. Build the knowledge base

    Documentation built from your code gives answers their context. We cover how in a walkthrough.

  3. Keep it current

    How the knowledge base stays current is shown in a walkthrough.

  4. Ask, listen, or connect an assistant

    Hear a walkthrough with its sources in view, or let your coding assistants use the same understanding.

Talk to us about understanding your codebase.

Contact us for enterprise access

Why Clarobase

Explanations that stay coupled to the code.

Not a chat about pasted code

Answers come from your connected repositories and the understanding Clarobase builds from them, with sources you can check.

Not a wiki you maintain

Knowledge that stays current without a documentation project.

Not a one-shot summary

Explanations, answers and your coding assistants all draw on the same understanding.

Security

Built for private code from day one.

Choose which repositories to connect and manage access by team space.

Isolated workspaces

Each customer gets its own workspace and sign-in.

Team space permissions

Access to answers follows team space membership.

You choose the access

You decide which repositories to connect.

Details on request

See the security and compliance overview for data handling and assurance status.

Security and compliance overview →

The evidence

Where developer time goes, and how far AI is trusted.

Independent research on code comprehension and AI use.

About 58%

of developer time went to program comprehension

Field study of 78 developers over 3,148 hours. Older study, before AI assistants. Xia et al., 2018

What developers say about AI answers

  • Ring gauge drawn to 66 percent 66%

    say "almost right, but not quite" is their biggest AI frustration

    Self-reported, 49,000+ respondents. Stack Overflow 2025

  • Ring gauge drawn to 45 percent 45%

    say debugging AI-generated code is more time-consuming

    Self-reported, same survey. Stack Overflow 2025

  • Ring gauge drawn to 75 percent 75%

    would still ask a person when they don't trust AI's answers

    Self-reported, same survey. Stack Overflow 2025

Share of changed lines, 2021 to 2024

Line chart of share of changed lines, 2021 to 2024, axis from 0 to 30 percent. Refactoring-associated lines: 25% in 2021 to under 10% in 2024. Cloned or copy-pasted lines: 8.3% in 2021 to 12.3% in 2024. Only the two published endpoints are plotted.
  • Refactoring-associated lines: 25% in 2021, under 10% in 2024
  • Cloned or copy-pasted lines: 8.3% in 2021, 12.3% in 2024

211 million changed lines, 2020 to 2024. "<10%" is plotted at 10%; GitClear reports under 10%. Only the published endpoints are shown. GitClear sells code analytics, and the data is correlational. GitClear 2025

Sources and caveats

Small studies measured comprehension before AI assistants, and the survey is self-reported. Your workspace’s Impact page tracks your own usage.

FAQ

Questions teams ask first.

Something else? Contact us and a person will answer.

Contact us
How is this different from asking a general AI chat about my code?

Clarobase answers from the repositories you connect, cites the source files, and respects team space permissions.

What can the code explainer do?

Ask how a feature works by voice or text and hear a spoken walkthrough, with sources you can check. It is meant to help your team understand and own its code, including code that AI wrote. We show it working on a real codebase in a walkthrough.

Why do documentation and a knowledge base matter for an explainer?

Clarobase builds a knowledge base from your code so explanations can draw on how features and services fit together.

How do coding agents use it?

Coding assistants can use the same repository context through a connector, within team space permissions.

What do I need to get started, and what is supported?

Connect the private GitHub repositories you choose. We’ll confirm fit during onboarding.

How can my enterprise get access?

Clarobase is available by invitation. Contact us with the form below or at [email protected]. We reply, walk you through the product, and talk through how your data would be handled before anything is connected.

Enterprise access

Bring Clarobase to your enterprise.

Available by invitation. Tell us about your team and the code you want to understand better.

  1. You contact us. Tell us about your team and your code.
  2. We reply and walk you through it. A person gets back to you by email.
  3. We talk about your data. How it would be handled, before anything is connected.

Review the draft and send it from your email app. You can also email [email protected].