Skip to content

Agentic AG Grid

Hire the engineer who puts agents inside your AG Grid.

Teams usually call me when

“Our users live in the grid, and the agent lives somewhere else.”

“We want to ask the data a question and see the answer in the grid.”

“Our AG Grid is slow, and now we want AI in it too.”

Two ways to put an agent in the grid

A copilot that drives the grid beside it, or a grid inside the chat. Both work through AG Grid’s own API, and every edit waits for a person.

Copilot beside the grid

Ask in plain English and the agent changes the grid you already have: filters, sorts and grouping, applied through the grid’s state API.

The grid in the chat stream

The answer arrives as a small grid inside the conversation. Users edit a cell there, and the change waits for approval before it applies.

How the weeks go

  • Grid and data auditand the first eval setWeek 1

  • Gatea performance baseline for the gridGo or no-go, end of week 2

  • Copilot actionsfilter, sort, group, through the grid APIWeeks 3 to 5

  • Grids in the chatcell edits behind approvalsWeeks 6 to 7

  • Handoffevals, runbooks, your engineersWeek 8

Week two measures the grid first. If it’s too slow for an agent yet, I fix that before adding one, and you keep the audit either way.

Done before

The SaberSim contests and players grid

SaberSim

A review that became a two-year rebuild of SaberSim’s lineup grid on AG Grid.

Users adjust projections and exposures in real time, in what used to be paginated HTML tables. I rebuilt it on AG Grid with NgRx and a measured performance budget, and exceptions and regressions dropped. Read the story

Runway and IFM run on grids I built. AG Grid partner since my first workshops for their customers.

For your security and procurement review

Your cloud accountyour keys, your data, your logsYour app and gridAG Grid Community or EnterpriseAgent backendallowed grid actions onlyYour data APIrows the user can already seeModel endpointyour provider, your keysLiveLoveAppoutsidepull requests,reviewsno copy ofyour data leaves
Data
Rows stay in your app and your data API. The agent sees only what the signed-in user can see.
Grid actions
An allow-list of grid API calls: filter, sort, group, column state and cell edits. Edits wait for a person to approve them.
Code and IP
Yours, in your repo, on your own AG Grid license.
Access
Least privilege, removed at handoff.
Paperwork
US LLC. Your MSA and NDA or mine. Professional liability insurance. W-9 on request.
Billing
Fixed scope per phase, invoiced net-30. The week-two baseline caps the risk.

Questions

Community or Enterprise?
Either. The agent works through the grid’s own state API, so it uses whatever features your license has.
Does the agent read the screen?
No. It calls the grid’s API for filters, sorts, grouping, column state and cell edits, so every action is typed, logged and testable.
Can it change our data?
Only through the cell edits you allow, and each one waits for a person to approve it before it reaches your API.
Do you work for AG Grid?
I’m an AG Grid partner and have taught their workshops at ng-conf, React Summit and React Advanced. On your project, I work for you.

Send me a screenshot of your grid and the question your users ask it.

I’ll reply within a business day with what an agent could do there first.

Send the screenshot →