blef
Joined 12 years ago
Joined 12 years ago
it's more how can we make sure in the thousands of rows/changes that we are reviewing every day we don't have invisible issues while keeping the code standards we expect
You can use the agent from any client (web, Slack, Teams but also other harnesses).
We think most of data analytics work will be transformed (and is already being transformed) from SQL monkeys to chat to analyses, but all the UI/UX are not designed for this and this is what nao is, being open-source because knowing how the context is managed is key.
With nao you can have a conversation and then shared the output on the form of a story, that can be either static or live replacing what old dashboards were.
We are close to 1k stars on Github: https://github.com/getnao/nao
Nonetheless I like this policy as well.
With nao we are exploring the fact that agents are good to work with filesystems, so we help people getting the context into the filesystem and then you can plug our agent loop on top (on anything else).
The most exciting part is working with sandboxes and emulating filesystems. So at the moment the filesystem is local, but it could be a bucket or a database that we emulate as real filesystem for the agentic loop, all of this can also be mounted to sandboxes, and in the end you can do data transformations all in isolation with control on the context.