Skip to main content

From sessions to answers.

Your coding agents already write down everything they do. Quesma collects those records, removes what should never leave a laptop, and turns the rest into a picture your whole organization can use.

The evidence is already on the laptop.

The record already exists

Claude Code, Codex, and Cursor keep local records of every session: prompts, tool calls, retries, and results. Quesma processes the files your agents already create.

Open-source collector

The collector that reads those files runs in your environment. Your engineers and security team can inspect every line.

Agents stay as they are

No proxy, rerouting, or changed behavior. Quesma never sits between developers and their agents.

Open data layer

Sessions land in open, documented tables you can query with the engines you already run. The record stays yours if you stop using Quesma.

Your bill shows tokens. Quesma shows the work.

Provider dashboards tell you how much your team used. They cannot tell you whether that usage fixed a bug, shipped a patch, or repeated the same failed approach for an hour.

  1. Repeated work

    The same test and context run again without a code change.

    YOUR TEAM CANStop costly retry loops.
  2. Model mismatch

    A high-cost model handles work that does not need its full capability.

    YOUR TEAM CANRoute routine work to a lower-cost model.
  3. Verified delivery

    Tested changes are separated from long sessions that ship nothing.

    YOUR TEAM CANScale the workflows that deliver.
Decisions based on the work record, not token totals alone.

Your sessions stay in your cloud.

Secrets, credentials, and sensitive values are removed on the developer machine, before anything is uploaded. The collector then writes directly to object storage your company controls.

YOUR DATA PLANE
  1. SOURCEAgent sessionsdeveloper environment
  2. LOCALCollection + redactionbefore upload
  3. OWNEDCustomer storageopen tables
  4. MEASUREQuesma analyticsnot in the upload path
MEASUREMENTINTERVENTION
The collector writes to your storage. Quesma is not in the upload path.

We analyze the agents. We don't score the engineers.

Quesma shows patterns across teams, repositories, and kinds of work. It does not turn those patterns into a ranking of people. Reading an individual's sessions takes permission, granted per role and never assumed.

Leadership sees the structure of the work, never a productivity score with an engineer's name attached.

  • employee AI score
  • employee token ranking
  • vibe coding compliance
  • personal slop quota

Asked before every rollout.

  1. Is this a surveillance tool?

    No, and the design shows it rather than promises it. Leadership and finance views are structural: teams, repositories, and kinds of work. There are no manager-facing leaderboards, and access to session content is explicit and role-based.

  2. Does our code leave our infrastructure?

    No. The open-source collector uploads directly to object storage your company owns, and sensitive values are removed on the developer’s machine before anything leaves it.

  3. Do we have to change how our agents run?

    No. Quesma reads the files your tools already produce. There is no proxy and no rerouting.

The record already exists. Start analyzing it.

Early access is opening soon for teams using Claude Code, Codex, or Cursor, ones where engineering and finance both need answers about agent spend.

Talk to the founder