Every channel has its own Claude, and Claude's access is configurable per-channel and per-workspace. Private channels don't leak information to other channels
This is one reason I think openai releasing a phone makes sense
If they can build an integrated AI assistant (what Siri should be) that can spin up and call agents it will be big (or it will flop but my money is on big if it’s the easiest way to use agents in your daily life)
I’ve been working on modernizing https://thelounge.chat, a self-hostable web based IRC client
Modernizing in two ways: migrating to new JS tooling (webpack -> vite, Node’s built in sqlite, etc) and adopting ircv3 features like emoji reactions, threaded replies, and typing indicators. Trying to bring IRC into the 21st century.
Its easy to contribute to and we have an active irc channel (perks of building an always-on client…) - feel free to join us! #thelounge on irc.libera.chat
Eh, we’re approaching that world (I am "an AI maximalist", I guess)
But someone with the knowledge to guide an AI will have more success than someone without, at least today. I don’t think that will necessarily be true in a year or two.
Each page navigation runs a WebGL shader that reads both the old and new page as live textures via the new texElementImage2D() API, then composites them through the selected compiz inspired effect.
But maybe there is some cool stuff here. A lot of prolific AI-assisted engineers I know have their own advanced plan modes, and the CEO plan mode in the repo is interesting (although very token heavy)
But then the LLM needs to write its own tools/code for interacting with said service. Which is fine, but slower and it can make mistakes vs officially provided tools
In v0, people can add e.g. Supabase, Neon, or Stripe to their projects with one click. We then auto-connect and auth to the integration’s remote MCP server on behalf of the user.
v0 can then use the tools the integration provider wants users to have, on behalf of the user, with no additional configuration. Query tables, run migrations, whatever. Zero maintenance burden on the team to manage the tools. And if users want to bring their own remote MCPs, that works via the same code path.
We also use various optimizations like a search_tools tool to avoid overfilling context
My friend and I were able to give claude a (no longer updated) unity arcade game. It decompiled it and created a one-to-one typescript port so it can run in the browser and now we're adding multiplayer support (for personal use, don't worry HN - we won't be distributing it). I'm very excited for what AI can do for legacy software.
v0 actually can directly copy files out of its examples and then apply edits. This saves it from having to write out the long examples verbatim. The rest of your comment is accurate