Adam Stachowiak

Now we have humans that are still there.

They're still the human in the loop or on the loop, depending upon the framework.

But that human is leveraging one or many agents or subagents.

to automate and to do different things in their tasks, whether it's designing the plan, whether it's writing all the code and they're reading the code, they're still doing the code review.

Maybe they're doing 20% of the coding because the agent does 80% of it or 90% of it or whatever the number is, you know, likely this person

has an agent.

And so we now have to look at the way we build tooling in a way that's like, okay, I used to do it this way, human only, but now the human has a friend, an agent, I can design for both of them because that human is expecting their agent to have agency on their behalf as they command it

To do the task.

And the agent speaks a different language, reads a different way, and interacts with a command line or an API in a different way.

And that's where MCP or even like cloud plugins come into play.

How do you feel about that world?

How do you feel about agents in our Postgres?

And now we can actually talk to our database.

Absolutely.

When I look at what you've done with, you know, agentic Postgres, which I think it's I'm not sure if you're trying to brand that term.

I think it is the first time I've heard it.

I wonder if that would just become the thing.

And it's a product named like Xerox or Kleenex.

And I won't be using Tiger Data's agent to Postgres.

I'll be using somebody else's because there are more Postgres database providers out there.