an architectural change we made in opencode2 is nearly everything is an internal plugin there's 68 of them that cover our built in agents, integrations, config loading, etc this means you can disable any behavior and we also properly dogfood our plugin apis

Meet Vault: Lemonade’s newest local security layer powered by AES-256 encryption. 🔒 Agents can use your keys without ever seeing them Zero leaks in chat logs. You keep full control with a personal 6-digit PIN. Your keys stay yours. Completely local. Completely safe. getlemonade.dev

The top Hermes integrations to give your agent superpowers: 1. Obsidian It works as a Karpathy-style second brain, but one that talks back. Every note, page, and backlink in the vault becomes live context. The agent doesn't just store knowledge, it reasons over it across everything that's been written and saved. 2. Playwright It gives Hermes a real browser instead of a read-only window to the web. It clicks, fills forms, and navigates pages the way a person would, then runs UI tests across Chromium, Firefox, and WebKit. This lets you turn Hermes from something that reads the web into something that can act on it. 3. InsForge It puts a full agentic backend behind one semantic layer. Auth, database, storage, and edge functions are all accessible without wiring five services together. The agent reasons about backend primitives directly instead of juggling disconnected APIs. GitHub: github.com/InsForge/insforge (don't forget to star 🌟) 4. GitHub It connects code, issues, and pull requests, turning Hermes into an engineering teammate that can actually read the repo. 5. Bright Data It hands agents web access that does not get blocked. It pulls live search results, full pages, and clean structured data from places like X, LinkedIn, and Reddit, handling the proxies, CAPTCHAs, and rendering underneath so the agent just gets usable data back. GitHub: github.com/brightdata/skills (don't forget to star 🌟) 6. Sequential thinking It upgrades how Hermes reasons rather than what it connects to. Most integrations give the agent new senses. This one gives it a better mindset. It forces Hermes to break a hard problem into ordered steps and revise its own plan as it goes, instead of committing to the first answer that looks right. 7. Google workspace It connects Gmail, Calendar, Drive, Docs, and Sheets in one place. The agent that can't check the inbox, read the calendar, or write to a shared doc is basically decorative. This should probably be the first integration anyone enables. 8. Zapier It acts as the layer that connects Hermes to everything else in the world. This single connector reaches thousands of downstream apps. Hermes can fire off a workflow, update a record, or move data between tools without anyone writing the glue code. 9. Stripe It surfaces revenue, refunds, subscription changes, and failed charges through a single question instead of clicking through dashboards. It turns Stripe from a payment processor into a queryable business intelligence layer. 10. Slack It handles channel-based automation inside Slack. Hermes can live inside specific channels with its own workflow in each. Support tickets from email get scanned, categorized, and dropped into the right channel every morning without anyone lifting a finger. It can also read on-call threads and post status updates so the team stops switching tabs to stay in sync. 11. Graphiti It builds real-time knowledge graphs of structured relationships from conversations and documents. Instead of flat vector similarity, the agent traverses typed connections between entities. That is the difference between finding similar text and understanding how things actually relate. GitHub: github.com/getzep/graphiti (don't forget to star 🌟) 12. Figma It gives the agent design context it can actually read. Hermes can pull a frame, read the tokens and layout, and turn it into code that respects the system down to the spacing. With FigJam it goes the other way too, generating architecture diagrams and ERDs straight from a prompt. It is underrated for anyone who lives between design and engineering. To dive deeper into Hermes, my co-founder wrote a full deep dive covering the Hermes agent's architecture, memory system, self-evolving skills, GEPA optimization, and how to set up multiple specialized agents. Read it below.

Profiles in @NousResearch Hermes Desktop Run sessions across profiles at once, switch between them mid-thread, and drag any chat (cross-profile or not) to reference it, set a color tag, idk you do you 🤍

Anthropic has confidentially submitted a draft S-1 registration statement to the Securities and Exchange Commission. Pending completion of SEC review, this gives us the option to pursue an initial public offering. Read more: anthropic.com/news/confident…

New in Claude Code: agent view. One list of all your sessions, available today as a research preview.

This works really well btw, at the end of your query ask your LLM to "structure your response as HTML", then view the generated file in your browser. I've also had some success asking the LLM to present its output as slideshows, etc. More generally, imo audio is the human-preferred input to AIs but vision (images/animations/video) is the preferred output from them. Around a ~third of our brains are a massively parallel processor dedicated to vision, it is the 10-lane superhighway of information into brain. As AI improves, I think we'll see a progression that takes advantage: 1) raw text (hard/effortful to read) 2) markdown (bold, italic, headings, tables, a bit easier on the eyes) <-- current default 3) HTML (still procedural with underlying code, but a lot more flexibility on the graphics, layout, even interactivity) <-- early but forming new good default ...4,5,6,... n) interactive neural videos/simulations Imo the extrapolation (though the technology doesn't exist just yet) ends in some kind of interactive videos generated directly by a diffusion neural net. Many open questions as to how exact/procedural "Software 1.0" artifacts (e.g. interactive simulations) may be woven together with neural artifacts (diffusion grids), but generally something in the direction of the recently viral xitter.cf/zan2434/status/2046982… There are also improvements necessary and pending at the input. Audio nor text nor video alone are not enough, e.g. I feel a need to point/gesture to things on the screen, similar to all the things you would do with a person physically next to you and your computer screen. TLDR The input/output mind meld between humans and AIs is ongoing and there is a lot of work to do and significant progress to be made, way before jumping all the way into neuralink-esque BCIs and all that. For what's worth exploring at the current stage, hot tip try ask for HTML.