984 karma · joined June 23, 2011
It grabbed my access tokens from cookies and curl into the app's private API for their UI. What an amazing time to be alive, can't wait for the future!
DuckDB has everything that streaming engines such as Flink have; it just needs to support managing intermediate aggregate states and scheduling the materialized views itself.
The hard work is done by PGlite and we use PGlite, it just enables PGlite to be accessible from everywhere.
The result is a PG server that fully lives in your browser: https://dbfor.dev
I have been trying a similar idea that takes your MCP configs and runs WASM JavaScript in case you're building a browser-based agent: https://github.com/buremba/1mcp
I'm okay with you sending me an email before you try, as long as explicit consent is given. However, if I don't care to change my primary card after the first attempt, that means I don't really care about continuing the subscription.
Happy to be wrong if you prove it with the data, though.
All the PostgreSQL data lives in your browser, and you have unlimited PostgreSQL servers that persist the data locally without installing anything.
- I switch in between planning and execution in the middle of the conversation using Terminal a lot, it would be nice to have it here as well rather than defining how I want Claude to think in advance.
- Entering messages when the agents can result in task lists to save time.
I’m also experimenting different UX with CC, here is Claude Code running in Slack if anybody is interested. https://peerbot.ai
I'm paying for Max, and when I use the tooling to calculate the spend returned by the API, I can see it's almost $1k! I have no idea how much quota I have left until the next block. The pricing returned by the API doesn't make any sense.
This should never happen; it's too risky to expose your production database to the AI agents. Always use read replicas for raw SQL access and expose API endpoints from your production database for write access. We will not be able to reliably solve the prompt injection attacks in the next 1-2 years.
We will likely see more middleware layers between the AI Agents and the production databases that can automate the data replication & security rules. I was just prototyping something for the weekend on https://dbfor.dev/
It's the same with another Soham, who was moonlighting for years. I would not be surprised if he starts a company soon, given the fame he has gained.
Marketing wins.
The more MCP tools I expose to the LLM, the harder it becomes for the LLM to get the job done. Instead, a single run_python tool works much better and faster. This is especially true for the reasoning models where context matters more.