Skip to content

← Aman Kumar Limited · RegisterNotes to the accounts · PULS

Flagship segment · agent · 2026 · Building

Pulse / Sense+

An analytics agent that answers product questions with your own permissions, read-only. Every number comes from a real query.

Role
Agent architecture, connectors and the Sense+ adapter
Lead
Outcome
In Sense+, Pulse answers product questions in plain English and scores 97% (165 / 170) on the analysis eval.
Links
Private codebase — described below
Stack
TypeScript · Next.js · Supabase · Claude Agent SDK · MCP SDK · DuckDB · libpg-query · Kysely · Zod

Problem

People can't get trustworthy answers from their own product data without knowing where to look. LLMs make the problem worse because they invent numbers.

What I built

  • One reasoning agent with typed tools, a semantic layer and compiler, and claims tied to result cells. answer() is the only way to finish a turn.
  • Three connectors. Sense+ through the user's own JWT and scope functions. Any MCP server through OAuth, with read-only tools and a DuckDB cache. A customer's read-only Postgres role.
  • Read-only at three layers. Every SQL text goes through Postgres's own parser, each connector asserts read-only, and the database role can't write. Tokens live in Supabase Vault, with one-click revoke.
  • Several surfaces. A web app, a one-script-tag embed SDK, a Chrome/Edge side-panel extension, and a worker on the Claude Agent SDK.
  • The Sense+ adapter. Planner → analysis engine → writer → validator, streamed over SSE, with hybrid retrieval and model re-ranking over the docs.

Result

97%Accuracy on the analysis evalsrc: Sense+ repo CLAUDE.md: 165 / 170

Under the hood

Host (embed · extension · web)
agent loop (plan
typed tools
compiled read-only SQL)
connector (Sense+ · MCP · Postgres)
answer card of verified claims
audit log
Host (embed · extension · web) → agent loop (plan → typed tools → compiled read-only SQL) → connector (Sense+ · MCP · Postgres) → answer card of verified claims → audit log

What I'd change

The eval suite would come before the second connector. The first 100%-gold spec caught more regressions than any code review.

Risk factors

  • Not generally available yet — it runs inside Sense+, and the standalone Pulse repo has no public history.
  • My share of the Sense+ repo is about 30% of commits; I own the agent, connectors and adapter, not the host product.

This is a portfolio, not an offer of securities. No shares exist. Figures are about shipped work.