Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

🚀 SimpleMem MCP is now LIVE & Open Source! Experience SimpleMem as a cloud-hosted memory service with fast retrieval, fewer tokens, and persistent memory - all exposed via MCP. Easily integrate with Cursor, Claude Desktop, LM Studio, Cherry Studio, and more. 👉 Try it now: 🔗 Code: Nice work... show more

Huaxiu Yao

6,700 subscribers

16,015 görüntüleme • 8 ay önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

🚀 SimpleMem now supports Claude Skills! Use SimpleMem in to remember long-term information and project history across conversations. Register at 👉 🔗 Detailed Code: Try it out and let us know what you think! @JiaqiLiu835914, Yaofeng Su, Peng (Richard) Xia, Siwei Han, Cihang Xie, Zeyu Zheng, Mingyu Ding

🚀 SimpleMem now supports Claude Skills! Use SimpleMem in to remember long-term information and project history across conversations. Register at 👉 🔗 Detailed Code: Try it out and let us know what you think! @JiaqiLiu835914, Yaofeng Su, Peng (Richard) Xia, Siwei Han, Cihang Xie, Zeyu Zheng, Mingyu Ding

Huaxiu Yao ✈️ ICML 2026

22,937 görüntüleme • 8 ay önce

🧠 Can agent memory scale without losing reasoning? 🔥 We’re excited to share our latest work, SimpleMem, a principled memory framework for LLM agents built around semantic lossless compression. 📉 30× fewer inference tokens 📈 +26.4% avg F1 (vs Mem0) ⚡ 50.2% faster retrieval (vs Mem0) Instead of storing raw interaction history 🗂️ or relying on costly iterative reasoning loops 🔁, SimpleMem treats memory as a structured, evolving representation whose primary objective is 🎯 maximizing information density per token. 📄 Paper: 🔗 Code: 📦 Website： Nice work @JiaqiLiu835914, Yaofeng Su, Peng (Richard) Xia, Siwei Han, and great collab. w/ Cihang Xie, Zeyu Zheng, Mingyu Ding

🧠 Can agent memory scale without losing reasoning? 🔥 We’re excited to share our latest work, SimpleMem, a principled memory framework for LLM agents built around semantic lossless compression. 📉 30× fewer inference tokens 📈 +26.4% avg F1 (vs Mem0) ⚡ 50.2% faster retrieval (vs Mem0) Instead of storing raw interaction history 🗂️ or relying on costly iterative reasoning loops 🔁, SimpleMem treats memory as a structured, evolving representation whose primary objective is 🎯 maximizing information density per token. 📄 Paper: 🔗 Code: 📦 Website： Nice work @JiaqiLiu835914, Yaofeng Su, Peng (Richard) Xia, Siwei Han, and great collab. w/ Cihang Xie, Zeyu Zheng, Mingyu Ding

Huaxiu Yao

119,895 görüntüleme • 8 ay önce

We’re excited to launch OpenMemory MCP, a private memory for MCP-compatible clients powered by mem0 Today, most AI assistants and dev tools operate without memory. You plan your roadmap in Claude, implement tasks in Cursor, but none of them know what the other did. Each tool operates in isolation, and your context disappears as soon as the session ends. OpenMemory MCP solves this. Built on the open Model Context Protocol (MCP), OpenMemory MCP runs 100% locally and provides a persistent, portable memory layer for all your AI tools. It enables agents and assistants to read from and write to a shared memory, securely and privately. Key capabilities: ✅Works across MCP clients like Cursor, Claude Desktop, Windsurf, Cline and more ✅Provides standardized memory operations (add_memories, search_memory, list_memories, delete_all_memories) ✅Stores data on your machine, fully private ✅Offers a centralized dashboard for visibility and control ✅Simple Docker-based setup with no vendor lock-in If you're building on MCP, OpenMemory MCP is the easiest way to add persistent, private memory to your clients with zero cloud dependencies and full local control. We’ve put together a short demo to show how it works Check it out in the links below 👇

We’re excited to launch OpenMemory MCP, a private memory for MCP-compatible clients powered by mem0 Today, most AI assistants and dev tools operate without memory. You plan your roadmap in Claude, implement tasks in Cursor, but none of them know what the other did. Each tool operates in isolation, and your context disappears as soon as the session ends. OpenMemory MCP solves this. Built on the open Model Context Protocol (MCP), OpenMemory MCP runs 100% locally and provides a persistent, portable memory layer for all your AI tools. It enables agents and assistants to read from and write to a shared memory, securely and privately. Key capabilities: ✅Works across MCP clients like Cursor, Claude Desktop, Windsurf, Cline and more ✅Provides standardized memory operations (add_memories, search_memory, list_memories, delete_all_memories) ✅Stores data on your machine, fully private ✅Offers a centralized dashboard for visibility and control ✅Simple Docker-based setup with no vendor lock-in If you're building on MCP, OpenMemory MCP is the easiest way to add persistent, private memory to your clients with zero cloud dependencies and full local control. We’ve put together a short demo to show how it works Check it out in the links below 👇

Taranjeet

472,273 görüntüleme • 1 yıl önce

$Data encryption is now live on Veilnet. Available in @veilnet/mcp-server@0.3.0. Any blob — file, dataset, config, recovery codes, contract draft, research note, agent memory — can now be encrypted on your device, shipped to Veilnet as ciphertext, and fetched back later without the decryption key ever leaving your machine. Three new MCP tools are live: data_store({ label, data }) encrypt + store data on Veilnetdata_fetch({ id }) fetch + decrypt locallydata_list() list stored ids With labels kept encrypted, the flow is simple: user data → encrypted locally → ciphertext stored on Veilnet → key remains on user device → agent fetches when needed → local decryption onlyVeilnet sees encrypted blobs. Your AI agent gets persistent private memory and secure storage.The provider does not need the raw data. This works in Claude Code, Claude Desktop, Cursor, Continue, and Cline. Install: npm i -g @veilnet/mcp-server Bootstrap your key at: → Agent tab Then ask any MCP-aware agent:“store this encrypted on Veilnet.”Docs:docs.veilnet.toPrivate prompts protected what users ask. Private MCP protected what agents run. Wallet Context protected what agents read. Encrypted data storage now protects what agents remember and reuse. All powered by $VEILNET$

Data encryption is now live on Veilnet. Available in @veilnet/[email protected]. Any blob — file, dataset, config, recovery codes, contract draft, research note, agent memory — can now be encrypted on your device, shipped to Veilnet as ciphertext, and fetched back later without the decryption key ever leaving your machine. Three new MCP tools are live: data_store({ label, data }) encrypt + store data on Veilnetdata_fetch({ id }) fetch + decrypt locallydata_list() list stored ids With labels kept encrypted, the flow is simple: user data → encrypted locally → ciphertext stored on Veilnet → key remains on user device → agent fetches when needed → local decryption onlyVeilnet sees encrypted blobs. Your AI agent gets persistent private memory and secure storage.The provider does not need the raw data. This works in Claude Code, Claude Desktop, Cursor, Continue, and Cline. Install: npm i -g @veilnet/mcp-server Bootstrap your key at: → Agent tab Then ask any MCP-aware agent:“store this encrypted on Veilnet.”Docs:docs.veilnet.toPrivate prompts protected what users ask. Private MCP protected what agents run. Wallet Context protected what agents read. Encrypted data storage now protects what agents remember and reuse. All powered by $VEILNET

Veilnet

11,761 görüntüleme • 3 ay önce

Qwen3.8-Flash is now live on QwenWork — twice as fast, and it gets you. Drop in your thoughts and files, and it automatically organizes your logic and generates decks with clear structure and professional polish, so you can focus on thinking and expressing. On Standard mode, 1,000 credits generate about 100 decks — roughly 10 credits each. That's real work done, on a real budget. 👉 Get your team on board and try it together: More API access： • Model Studio: • Qwen Cloud: #QwenWork #AI #Qwen38Flash #AIAgent

Qwen3.8-Flash is now live on QwenWork — twice as fast, and it gets you. Drop in your thoughts and files, and it automatically organizes your logic and generates decks with clear structure and professional polish, so you can focus on thinking and expressing. On Standard mode, 1,000 credits generate about 100 decks — roughly 10 credits each. That's real work done, on a real budget. 👉 Get your team on board and try it together: More API access： • Model Studio: • Qwen Cloud: #QwenWork #AI #Qwen38Flash #AIAgent

Alibaba Cloud

21,872 görüntüleme • 24 gün önce

If you use Cursor for coding, Claude Code for debugging, and local agents for automation, you almost certainly have a context problem. Every tool acts like an isolated employee. One assistant forgets what the other just learned. The biggest bottleneck in multi-agent workflows right now isn’t reasoning. It’s collective amnesia, combined with zero communication between agents. Memmy just launched a smart fix for this: a local, cross-agent memory layer. Instead of re-pasting your context everywhere, Memmy gives your stack a shared memory hub: → accumulate knowledge once, then use it across Cursor, Codex, and OpenClaw → automatically scan and import your existing agent history, so you don’t have to start from zero → keep your memory local, while model usage depends on your chosen provider or BYOK setup And it isn’t just a memory plugin. It’s a complete personal AI runtime with both MCP and a CLI. Memmy officially launched on Product Hunt, and the team is giving early users experiencing context fragmentation a free trial with 2M GPT tokens. Check it out and support the team with an upvote: → Best part? It’s also open-source for devs who want to build their own agents 🔥 Repo in 🧵↓

If you use Cursor for coding, Claude Code for debugging, and local agents for automation, you almost certainly have a context problem. Every tool acts like an isolated employee. One assistant forgets what the other just learned. The biggest bottleneck in multi-agent workflows right now isn’t reasoning. It’s collective amnesia, combined with zero communication between agents. Memmy just launched a smart fix for this: a local, cross-agent memory layer. Instead of re-pasting your context everywhere, Memmy gives your stack a shared memory hub: → accumulate knowledge once, then use it across Cursor, Codex, and OpenClaw → automatically scan and import your existing agent history, so you don’t have to start from zero → keep your memory local, while model usage depends on your chosen provider or BYOK setup And it isn’t just a memory plugin. It’s a complete personal AI runtime with both MCP and a CLI. Memmy officially launched on Product Hunt, and the team is giving early users experiencing context fragmentation a free trial with 2M GPT tokens. Check it out and support the team with an upvote: → Best part? It’s also open-source for devs who want to build their own agents 🔥 Repo in 🧵↓

Charly Wargnier

203,456 görüntüleme • 1 ay önce

MCP is an absolute game-changer. (Together with DeepSeek, MCP is probably the hottest thing in AI over the last 6 months.) I use Cursor to write code 90% of the time. I built an MCP server to connect the Cursor agent to GroundX, an open-source RAG system, and I'm not going back. This is officially insane! Here is what I did, step by step: First, a little bit of context. I maintain an end-to-end Machine Learning System with several pipelines to process data, train, evaluate, register, deploy, and monitor a model. I've written a lot of documentation explaining how the system works and how to modify and maintain it. There's also the documentation of the few libraries I used to build the system. I'm a massive fan of GroundX, an open-source enterprise-grade RAG system you can run on your servers or deploy to any cloud provider. I've been working with them for a long time. GroundX offers two services. First, the "ingest" service uses a custom, pretrained vision model to ingest and understand your data. I used this to process all the documentation I have for my code. Markdown files, source code, HTML files, and even PDF documents. Everything I've written related to my project went into GroundX. Their second service is "search," which combines text and vector search with a fine-tuned re-ranker model to retrieve information from the data. I needed to connect Cursor with this service, and that's where MCP came in. I built an MCP server with two tools: 1. The first tool would go to GroundX and retrieve the available topics. Splitting the data into topics (or "buckets," as GroundX calls them) allows me to use the same setup to serve documentation from different topics. 2. The second tool would search GroundX under a specific topic for the context related to the supplied query. The magic happens after connecting the MCP server with Cursor. Now, I can ask any questions related to my project, and Cursor's AI agent retrieves the list of available topics from the RAG system and then searches it to provide relevant context to the model. I went from getting mediocre, sometimes wrong answers to 100% truthful, complete answers. Here is the crazy part:

MCP is an absolute game-changer. (Together with DeepSeek, MCP is probably the hottest thing in AI over the last 6 months.) I use Cursor to write code 90% of the time. I built an MCP server to connect the Cursor agent to GroundX, an open-source RAG system, and I'm not going back. This is officially insane! Here is what I did, step by step: First, a little bit of context. I maintain an end-to-end Machine Learning System with several pipelines to process data, train, evaluate, register, deploy, and monitor a model. I've written a lot of documentation explaining how the system works and how to modify and maintain it. There's also the documentation of the few libraries I used to build the system. I'm a massive fan of GroundX, an open-source enterprise-grade RAG system you can run on your servers or deploy to any cloud provider. I've been working with them for a long time. GroundX offers two services. First, the "ingest" service uses a custom, pretrained vision model to ingest and understand your data. I used this to process all the documentation I have for my code. Markdown files, source code, HTML files, and even PDF documents. Everything I've written related to my project went into GroundX. Their second service is "search," which combines text and vector search with a fine-tuned re-ranker model to retrieve information from the data. I needed to connect Cursor with this service, and that's where MCP came in. I built an MCP server with two tools: 1. The first tool would go to GroundX and retrieve the available topics. Splitting the data into topics (or "buckets," as GroundX calls them) allows me to use the same setup to serve documentation from different topics. 2. The second tool would search GroundX under a specific topic for the context related to the supplied query. The magic happens after connecting the MCP server with Cursor. Now, I can ask any questions related to my project, and Cursor's AI agent retrieves the list of available topics from the RAG system and then searches it to provide relevant context to the model. I went from getting mediocre, sometimes wrong answers to 100% truthful, complete answers. Here is the crazy part:

Santiago

255,756 görüntüleme • 1 yıl önce

Look ma new Codex Updates! 0.119.0 and 0.120.0 are here. And with it, a HUGE number of quality of life updates and bug fixes! > Hooks now render in a dedicated live area above the composer. They only persist when they have output, so your terminal stays clean. If you're running PreToolUse or PostToolUse hooks, this is a huge readability win. > Hooks are now available again on Windows > CTRL+O copies the last agent output. Small but clutch when you're pulling a code block into another file or chat. > New statusline option: context usage as a graphical bar instead of a percentage. Easier to glance at mid-session when you're trying to gauge how much runway you have left. > Zellij support is here with no scrollback bugs. If you've been stuck on tmux just because Codex was broken in Zellij, you're free now (shout out Felipe Coury 🦀) > Memory extensions just landed. The consolidation agent can now discover plugin folders under memories_extensions/ and read their instructions.md to learn how to interpret new memory sources. Drop a folder in, give it guidance, and the agent picks it up automatically during summarization. No core code changes needed. This is the first real extension point for Codex's memory system, and it opens the door for third-party memory plugins. > Did you know, you can /rename a thread? But what's really cool about that is, after you rename it, you can resume it with the same name, no more UUIDs. codex resume mynewapp or directly from the TUI: /resume mynewapp > Multi agents v2 got an update to tool descriptions More reliable multi agent environments and inter agent communication > You can now enable TUI notifications whether Codex is in focus or not. Modify this in your config: [tui] notification_condition = "always" > MAJOR overhaul to Codex MCP functionality: 1. Codex Tool Search now works with custom MCP servers, so tools can be searched and deferred instead of all being exposed up front. 2. Custom MCP servers can now trigger elicitations, meaning they can stop and ask for user approval or input mid-flow. 3. MCP tool results now preserve richer metadata, which improves app/UI handoff behavior. 4. Codex can now read MCP resources directly, letting apps return resource URIs that the client can actually open. 5. File params for Codex Apps are smoother: local file paths can be uploaded and remapped automatically. 6. Plugin cache refresh and fallback sync behavior are more reliable, especially for custom and curated plugins. > Composer and chat behavior smoother overall, resize bugs remain though. > Realtime v2 got several significant improvements as well. > You're still reading? What a legend. 🫶 npm i -g @openai/codex to update

Look ma new Codex Updates! 0.119.0 and 0.120.0 are here. And with it, a HUGE number of quality of life updates and bug fixes! > Hooks now render in a dedicated live area above the composer. They only persist when they have output, so your terminal stays clean. If you're running PreToolUse or PostToolUse hooks, this is a huge readability win. > Hooks are now available again on Windows > CTRL+O copies the last agent output. Small but clutch when you're pulling a code block into another file or chat. > New statusline option: context usage as a graphical bar instead of a percentage. Easier to glance at mid-session when you're trying to gauge how much runway you have left. > Zellij support is here with no scrollback bugs. If you've been stuck on tmux just because Codex was broken in Zellij, you're free now (shout out Felipe Coury 🦀) > Memory extensions just landed. The consolidation agent can now discover plugin folders under memories_extensions/ and read their instructions.md to learn how to interpret new memory sources. Drop a folder in, give it guidance, and the agent picks it up automatically during summarization. No core code changes needed. This is the first real extension point for Codex's memory system, and it opens the door for third-party memory plugins. > Did you know, you can /rename a thread? But what's really cool about that is, after you rename it, you can resume it with the same name, no more UUIDs. codex resume mynewapp or directly from the TUI: /resume mynewapp > Multi agents v2 got an update to tool descriptions More reliable multi agent environments and inter agent communication > You can now enable TUI notifications whether Codex is in focus or not. Modify this in your config: [tui] notification_condition = "always" > MAJOR overhaul to Codex MCP functionality: 1. Codex Tool Search now works with custom MCP servers, so tools can be searched and deferred instead of all being exposed up front. 2. Custom MCP servers can now trigger elicitations, meaning they can stop and ask for user approval or input mid-flow. 3. MCP tool results now preserve richer metadata, which improves app/UI handoff behavior. 4. Codex can now read MCP resources directly, letting apps return resource URIs that the client can actually open. 5. File params for Codex Apps are smoother: local file paths can be uploaded and remapped automatically. 6. Plugin cache refresh and fallback sync behavior are more reliable, especially for custom and curated plugins. > Composer and chat behavior smoother overall, resize bugs remain though. > Realtime v2 got several significant improvements as well. > You're still reading? What a legend. 🫶 npm i -g @openai/codex to update

am.will

742,455 görüntüleme • 5 ay önce

Claude Code is now scary good at full-stack! I asked it to build a real-time weather intelligence dashboard with an interactive 3D globe and a forecasting layer that predicts weather 3 days ahead. It came back with a spinning globe that has a day/night cycle using NASA satellite imagery, city lights on the dark side, weather icons that switch between sun and moon based on local time, and a time travel slider that scrubs through 10 days of data. Claude Code built the whole thing in a single session, including the backend, database, data pipeline, and frontend. For the database, I needed something fast for time-series workloads since the app ingests hourly weather readings across many cities and serves time-range queries on every slider interaction. I used Tiger Cloud by Tiger Data - Creators of TimescaleDB, which gives you managed TimescaleDB on the Postgres you already know. Claude Code connected to it through the Tiger CLI MCP server and set up the entire backend directly: - Provisioned the database service - Created hypertables for time-partitioned weather storage - Set up continuous aggregates for pre-computed rollups - Built the data ingestion pipeline and the full NextJS + ThreeJS frontend The time travel slider queries thousands of rows on every position change. On a regular Postgres table, this would require manual partitioning and index tuning to stay fast as data grows. TimescaleDB partitions the data by timestamp automatically, so each query only hits the relevant time chunk. Continuous aggregates serve the trend charts and forecast layer from pre-computed rollups instead of rescanning raw data on every request. The video below shows the final build in action, and I worked with the Tiger Data team to put this together. Tiger CLI is open-source (Apache 2.0) and works with Claude Code, Cursor, Codex, Gemini CLI, and VS Code. To try this yourself: → Sign up for Tiger Cloud (I have shared the link in the replies). It gives you $1,000 free credits (no card needed) → Install Tiger CLI: curl -fsSL https(:)//cli(.)tigerdata(.)com | sh → Run tiger mcp install claude-code → Give Claude Code a prompt and let it build Find the sign-up link in the replies.

Claude Code is now scary good at full-stack! I asked it to build a real-time weather intelligence dashboard with an interactive 3D globe and a forecasting layer that predicts weather 3 days ahead. It came back with a spinning globe that has a day/night cycle using NASA satellite imagery, city lights on the dark side, weather icons that switch between sun and moon based on local time, and a time travel slider that scrubs through 10 days of data. Claude Code built the whole thing in a single session, including the backend, database, data pipeline, and frontend. For the database, I needed something fast for time-series workloads since the app ingests hourly weather readings across many cities and serves time-range queries on every slider interaction. I used Tiger Cloud by Tiger Data - Creators of TimescaleDB, which gives you managed TimescaleDB on the Postgres you already know. Claude Code connected to it through the Tiger CLI MCP server and set up the entire backend directly: - Provisioned the database service - Created hypertables for time-partitioned weather storage - Set up continuous aggregates for pre-computed rollups - Built the data ingestion pipeline and the full NextJS + ThreeJS frontend The time travel slider queries thousands of rows on every position change. On a regular Postgres table, this would require manual partitioning and index tuning to stay fast as data grows. TimescaleDB partitions the data by timestamp automatically, so each query only hits the relevant time chunk. Continuous aggregates serve the trend charts and forecast layer from pre-computed rollups instead of rescanning raw data on every request. The video below shows the final build in action, and I worked with the Tiger Data team to put this together. Tiger CLI is open-source (Apache 2.0) and works with Claude Code, Cursor, Codex, Gemini CLI, and VS Code. To try this yourself: → Sign up for Tiger Cloud (I have shared the link in the replies). It gives you $1,000 free credits (no card needed) → Install Tiger CLI: curl -fsSL https(:)//cli(.)tigerdata(.)com | sh → Run tiger mcp install claude-code → Give Claude Code a prompt and let it build Find the sign-up link in the replies.

Avi Chawla

14,838 görüntüleme • 4 ay önce

20 GitHub repos with 2.4M+ combined stars that replace tools costing $60,000+/year 1. public-apis ⭐456k - 1,500+ free APIs across every category, weather to finance to games, all documented. 2. awesome-selfhosted ⭐312k - self-hosted replacements for Notion, Google Photos, Zapier, and dozens more paid subscriptions. 3. hermes-agent ⭐230k - self-improving personal agent with persistent memory, cron scheduling, MCP built in. Free alternative to paid always-on agent platforms. 4. n8n ⭐200k - visual automation with native AI agents. Replaces Zapier/Make entirely, self-hosted. 5. ollama ⭐178k - run Llama, Mistral, DeepSeek locally with one command. No API bill, no rate limits. 6. dify ⭐152k - visual builder for AI agents and RAG pipelines. Skip the $500/mo no-code AI builder subscription. 7. free-for-dev ⭐132k - hundreds of services with permanent free tiers. No trials, no credit card. 8. awesome-llm-apps ⭐132k - 100+ ready AI agents and RAG apps with full code. 9. awesome-mcp-servers ⭐92k - thousands of MCP servers connecting your agent to browsers, databases, anything. 10. supabase ⭐108k - Firebase alternative that's actually free to start. Auth, DB, storage in one Claude Code prompt. 11. strapi ⭐73k - open-source headless CMS, generates a full API from your content model in minutes. No Contentful bill. 12. immich ⭐110k - self-hosted photo and video backup with face recognition. Cancel the Google Photos storage plan. 13. appwrite ⭐57k - complete backend-as-a-service, self-hosted. Auth, DB, functions, storage, one prompt away from Firebase money. 14. medusa ⭐36k - full ecommerce backend, open source. Skip Shopify Plus fees entirely on your next vibe-coded store. 15. novu ⭐39k - notification infrastructure for email, SMS, push, in-app, all in one API. Replaces OneSignal's paid tiers. 16. tooljet ⭐38k - drag-and-drop internal tool builder connected to any database or API. Retool's seat pricing gone. 17. mattermost ⭐38k - self-hosted team chat built for engineering orgs. Slack without the per-seat bill. 18. outline ⭐40k - fast, clean team wiki and docs. Replaces Confluence and Notion's team plan. 19. plausible ⭐28.5k - privacy-friendly analytics, lightweight script, real dashboards. No GA360 contract needed. 20. openwork ⭐22k - open-source Claude Cowork alternative. Share skills and MCPs across Claude Code, Cursor, Codex, one setup for every agent. Save this before you pay for another tool this list already replaces for free 👇

20 GitHub repos with 2.4M+ combined stars that replace tools costing $60,000+/year 1. public-apis ⭐456k - 1,500+ free APIs across every category, weather to finance to games, all documented. 2. awesome-selfhosted ⭐312k - self-hosted replacements for Notion, Google Photos, Zapier, and dozens more paid subscriptions. 3. hermes-agent ⭐230k - self-improving personal agent with persistent memory, cron scheduling, MCP built in. Free alternative to paid always-on agent platforms. 4. n8n ⭐200k - visual automation with native AI agents. Replaces Zapier/Make entirely, self-hosted. 5. ollama ⭐178k - run Llama, Mistral, DeepSeek locally with one command. No API bill, no rate limits. 6. dify ⭐152k - visual builder for AI agents and RAG pipelines. Skip the $500/mo no-code AI builder subscription. 7. free-for-dev ⭐132k - hundreds of services with permanent free tiers. No trials, no credit card. 8. awesome-llm-apps ⭐132k - 100+ ready AI agents and RAG apps with full code. 9. awesome-mcp-servers ⭐92k - thousands of MCP servers connecting your agent to browsers, databases, anything. 10. supabase ⭐108k - Firebase alternative that's actually free to start. Auth, DB, storage in one Claude Code prompt. 11. strapi ⭐73k - open-source headless CMS, generates a full API from your content model in minutes. No Contentful bill. 12. immich ⭐110k - self-hosted photo and video backup with face recognition. Cancel the Google Photos storage plan. 13. appwrite ⭐57k - complete backend-as-a-service, self-hosted. Auth, DB, functions, storage, one prompt away from Firebase money. 14. medusa ⭐36k - full ecommerce backend, open source. Skip Shopify Plus fees entirely on your next vibe-coded store. 15. novu ⭐39k - notification infrastructure for email, SMS, push, in-app, all in one API. Replaces OneSignal's paid tiers. 16. tooljet ⭐38k - drag-and-drop internal tool builder connected to any database or API. Retool's seat pricing gone. 17. mattermost ⭐38k - self-hosted team chat built for engineering orgs. Slack without the per-seat bill. 18. outline ⭐40k - fast, clean team wiki and docs. Replaces Confluence and Notion's team plan. 19. plausible ⭐28.5k - privacy-friendly analytics, lightweight script, real dashboards. No GA360 contract needed. 20. openwork ⭐22k - open-source Claude Cowork alternative. Share skills and MCPs across Claude Code, Cursor, Codex, one setup for every agent. Save this before you pay for another tool this list already replaces for free 👇

unicode

34,424 görüntüleme • 1 ay önce

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)

elvis

15,614 görüntüleme • 2 ay önce

Claude Code is now scary good at full-stack! I asked it to build a real-time weather intelligence dashboard with an interactive 3D globe, a forecasting layer that predicts weather 3 days ahead, and an anomaly detector that flags cities whose weather is behaving abnormally. It came back with a spinning globe that has a day/night cycle using NASA satellite imagery, city lights on the dark side, weather icons that switch between sun and moon based on local time, and a time travel slider that scrubs through 10 days of data. And when a city's weather breaks from its own normal, it pulses red (abnormally hot) or blue (abnormally cold) right on the globe, updating live and reflecting the anomaly state at any point you drag the slider to. Claude Code built the whole thing in a single session, including the backend, database, data pipeline, and frontend. For the database, I needed something fast for time-series workloads since the app ingests hourly weather readings across many cities and serves time-range queries on every slider interaction. I used Tiger Cloud by Tiger Data - Creators of TimescaleDB, which gives you managed TimescaleDB on the Postgres you already know. Claude Code connected to it through the Tiger CLI MCP server and set up the entire backend directly: - Provisioned the database service - Created hypertables for time-partitioned weather storage - Set up continuous aggregates for pre-computed rollups - Built the data ingestion pipeline and the full NextJS + ThreeJS frontend The time travel slider queries thousands of rows on every position change. On a regular Postgres table, this would require manual partitioning and index tuning to stay fast as data grows. TimescaleDB partitions the data by timestamp automatically, so each query only hits the relevant time chunk. Continuous aggregates serve the trend charts, the forecast layer, and the anomaly baselines from pre-computed rollups instead of rescanning raw data on every request. The video below shows the final build in action, and I worked with the Tiger Data team to put this together. Tiger CLI is open-source (Apache 2.0) and works with Claude Code, Cursor, Codex, Gemini CLI, and VS Code. To try this yourself: → Sign up for Tiger Cloud (I have shared the link in the replies). It gives you $1,000 free credits (no card needed) → Install Tiger CLI: curl -fsSL https(:)//cli(.)tigerdata(.)com | sh → Run tiger mcp install claude-code → Give Claude Code a prompt and let it build sign-up here: My co-founder also wrote a detailed article on this. The article is quoted below.

Claude Code is now scary good at full-stack! I asked it to build a real-time weather intelligence dashboard with an interactive 3D globe, a forecasting layer that predicts weather 3 days ahead, and an anomaly detector that flags cities whose weather is behaving abnormally. It came back with a spinning globe that has a day/night cycle using NASA satellite imagery, city lights on the dark side, weather icons that switch between sun and moon based on local time, and a time travel slider that scrubs through 10 days of data. And when a city's weather breaks from its own normal, it pulses red (abnormally hot) or blue (abnormally cold) right on the globe, updating live and reflecting the anomaly state at any point you drag the slider to. Claude Code built the whole thing in a single session, including the backend, database, data pipeline, and frontend. For the database, I needed something fast for time-series workloads since the app ingests hourly weather readings across many cities and serves time-range queries on every slider interaction. I used Tiger Cloud by Tiger Data - Creators of TimescaleDB, which gives you managed TimescaleDB on the Postgres you already know. Claude Code connected to it through the Tiger CLI MCP server and set up the entire backend directly: - Provisioned the database service - Created hypertables for time-partitioned weather storage - Set up continuous aggregates for pre-computed rollups - Built the data ingestion pipeline and the full NextJS + ThreeJS frontend The time travel slider queries thousands of rows on every position change. On a regular Postgres table, this would require manual partitioning and index tuning to stay fast as data grows. TimescaleDB partitions the data by timestamp automatically, so each query only hits the relevant time chunk. Continuous aggregates serve the trend charts, the forecast layer, and the anomaly baselines from pre-computed rollups instead of rescanning raw data on every request. The video below shows the final build in action, and I worked with the Tiger Data team to put this together. Tiger CLI is open-source (Apache 2.0) and works with Claude Code, Cursor, Codex, Gemini CLI, and VS Code. To try this yourself: → Sign up for Tiger Cloud (I have shared the link in the replies). It gives you $1,000 free credits (no card needed) → Install Tiger CLI: curl -fsSL https(:)//cli(.)tigerdata(.)com | sh → Run tiger mcp install claude-code → Give Claude Code a prompt and let it build sign-up here: My co-founder also wrote a detailed article on this. The article is quoted below.

Akshay 🚀

37,269 görüntüleme • 1 ay önce

This one’s big. Atlassian just dropped something a lot of us have been waiting for. Rovo Dev is an AI coding assistant that finally fits how Atlassian teams actually work! 🔥 Think Claude Code, but with some unique twists: → Built-in integration with Atlassian Jira, Atlassian Confluence, and Atlassian Bitbucket → Persistent memory across sessions for ongoing collaboration → Enterprise-grade controls: permissions, audit logs, zero data retention by default (!!) It also supports model routing across OpenAI, Anthropic, and open-source models like Llama / Gemma... not something you'd get with Claude or Gemini CLI! 👇 But here’s the real kicker: Rovo uses Atlassian’s Teamwork Graph to surface data from your Jira issues, Confluence docs, and code repos. So when Rovo answers, it’s not guessing: it’s grounded in your actual projects, teams, and task history 🧠 It also speaks MCP, so you can hook in other tools and data sources to take it even further. During my tests, I had Rovo Dev build a full app from scratch. It managed the entire flow autonomously, with updates instantly reflected across Jira and Confluence. IMO for anyone using Atlassian tools a lot, Rovo's a no brainer. I don’t use Jira much these days, but after years deep in it, I really wish this had existed back then! :) Big thanks to Atlassian for the collab, I learned a ton in the process! More about Rovo Dev here →

This one’s big. Atlassian just dropped something a lot of us have been waiting for. Rovo Dev is an AI coding assistant that finally fits how Atlassian teams actually work! 🔥 Think Claude Code, but with some unique twists: → Built-in integration with Atlassian Jira, Atlassian Confluence, and Atlassian Bitbucket → Persistent memory across sessions for ongoing collaboration → Enterprise-grade controls: permissions, audit logs, zero data retention by default (!!) It also supports model routing across OpenAI, Anthropic, and open-source models like Llama / Gemma... not something you'd get with Claude or Gemini CLI! 👇 But here’s the real kicker: Rovo uses Atlassian’s Teamwork Graph to surface data from your Jira issues, Confluence docs, and code repos. So when Rovo answers, it’s not guessing: it’s grounded in your actual projects, teams, and task history 🧠 It also speaks MCP, so you can hook in other tools and data sources to take it even further. During my tests, I had Rovo Dev build a full app from scratch. It managed the entire flow autonomously, with updates instantly reflected across Jira and Confluence. IMO for anyone using Atlassian tools a lot, Rovo's a no brainer. I don’t use Jira much these days, but after years deep in it, I really wish this had existed back then! :) Big thanks to Atlassian for the collab, I learned a ton in the process! More about Rovo Dev here →

Charly Wargnier

58,153 görüntüleme • 11 ay önce

three․ws is the 3D AI agent layer of the open web. Anyone can generate a 3D avatar, give it an LLM brain, register it on-chain across multiple blockchains, embed it anywhere, and let it earn and spend money on its own. Agents have embodied WebGL identities that express emotion through morph-target blending, animate, respond to voice, API calls, and datastreams, hold their own wallets, and persist memory. Open source, live today. It starts with generation. Forge turns a text prompt, one to four photos, or a rough sketch into a textured downloadable GLB. Selfies become rigged avatars in about a minute. Quality tiers run from draft to 200k-poly PBR. From there every model can be auto-rigged, restyled, retextured, segmented, embedded, or deployed on-chain. The same engine ships as a REST API, an x402 pay-per-call twin, and a 3D Studio MCP server with 15 tools. The brain runs on IBM Granite via IBM watsonx plus Claude (users may decide which model they prefer), with a structured tool-loop. A multi-LLM mode streams Claude, GPT, Qwen, ModelScope, and Groq side by side. An empathy layer blends emotion from protocol events rather than a state machine. Voice covers cloning, a Voice Lab, real-time ARKit-52 lip-sync, and mic-driven lip-sync. Skills install from IPFS, Arweave, or HTTP, and memory is pinned to IPFS with R2 and Postgres modes. Identity is cross-chain, not Solana only. ERC-8004 contracts (Identity, Reputation, Validation) deploy on any of 15+ EVM chains, alongside a program-free Metaplex Core analog on Solana. Every agent gets a stable ID, owner wallet, EIP-712 delegated signer, IPFS manifest, a cryptographically signed action log, and EIP-7710 delegated permissions for agent-to-agent authorization. While multichain, the THREE token is only available on Solana with no plans to go cross-chain, the team has no plans to endorse or support any other coins. Then the economy. $THREE is the platform's only token and pay-per-use currency, with holder tiers and rewards. x402 powers pay-per-call micropayments in USDC and soon THREE on Solana, with pay-by-name resolution, a Bazaar marketplace, arbitrage, and on-chain skills. All production ready and shipped, ready to be integrated in partnered projects, open-source by default for anyone to adopt. Three ships a Pump.fun intelligence stack. Launch a coin for your agent, score every launch 0 to 100 with the Oracle conviction engine, scan new coins in their first 90 seconds, track smart money against coins that actually graduated, rank traders by provable on-chain record, and watch autonomous agents trade live in the Sniper Arena. The 3D AI Agent world is multiplayer. Every Solana token gets a live deterministic 3D world with peer avatars, chat, emotes, and voxel building thanks to Coin Communities. There is a walkable City, an authoritative Colyseus-backed Walk with AR passthrough, a Club with rigged dancers and micro-tips, friends, presence, and DMs, and an IRL mode that places agents in your real environment, private by physical location. AR is shipped today on WebXR and iOS Quick Look. Robotics is the long-horizon extension. For builders: Scene Studio, Scene Composer, an Animation Studio that sells clips for USDC, a glTF validator, an web component, five widget types, a WYSIWYG embed editor, hosted Launchpad pages, claimable *.threews.sol names, an OAuth 2.1 server, an MCP server with paid tools, published SDKs, and an OpenAPI spec. Listed across IBM, AWS, Alibaba Cloud, BNB Dappbay, the MCP Registry, and Solana Mobile Seeker. Architecture is four layers (viewer, runtime, identity, embed) on a single event bus. The roadmap is four phases: foundations (shipped), selfie-to-avatar engine, agent personalization with voice cloning, the on-chain economy, and an open decentralized inference network where agents pay GPU nodes on-chain for compute. The goal is simple: move AI from centralized SaaS into persistent, ownable, protocol-based entities in a real machine economy, bridging digital entities into the real world. Welcome to the 3D Layer of the Internet. This is three․ws.

three.ws

20,471 görüntüleme • 3 ay önce

This is how you get 15x fable 5 usage. Fable -> Composer 2.5 reading Fable -> GPT 5.5 execution I built CNVS to make agent orchestration dead simple and insanely visual. You can watch fable 5 delegate work to cursor, codex, open code, all your agents. using your exsisting ai subs no api pricing. The canvas is fully voice controlled locally with nvidia parakeet for fast and free, or gpt realtime 2 for a fully conversational jarvis experience. The built in mcp and cli means agentic control is bidirectional they can prompt and spawn each other and read agent states. but there is more I built it from the ground up in swift for native performance on mac os. My old 16gb m1 mbp can easily spin up and control eight agents across multiple canvasses. The hermes integration + remote canvases allow you to run agents fully in the cloud on your VPS think google docs of vibe coding. You can literally turn off your mac and they keep working, open cnvs back up and pick up where you left off. I built a cross agent memory system based on 2026 research so all your agents feel like one brain. its SIMPLE and on demand. This eliminates context bloat, and the research supports a massive uptick in cross agent performance. There is soo much more. PS - I am a father building this project 100% solo in my basement on live stream everyday, my goal is to push vibe coding to the next level PPS - CNVS is a lifetime license becuase you DO NOT need another subscription in your life.

This is how you get 15x fable 5 usage. Fable -> Composer 2.5 reading Fable -> GPT 5.5 execution I built CNVS to make agent orchestration dead simple and insanely visual. You can watch fable 5 delegate work to cursor, codex, open code, all your agents. using your exsisting ai subs no api pricing. The canvas is fully voice controlled locally with nvidia parakeet for fast and free, or gpt realtime 2 for a fully conversational jarvis experience. The built in mcp and cli means agentic control is bidirectional they can prompt and spawn each other and read agent states. but there is more I built it from the ground up in swift for native performance on mac os. My old 16gb m1 mbp can easily spin up and control eight agents across multiple canvasses. The hermes integration + remote canvases allow you to run agents fully in the cloud on your VPS think google docs of vibe coding. You can literally turn off your mac and they keep working, open cnvs back up and pick up where you left off. I built a cross agent memory system based on 2026 research so all your agents feel like one brain. its SIMPLE and on demand. This eliminates context bloat, and the research supports a massive uptick in cross agent performance. There is soo much more. PS - I am a father building this project 100% solo in my basement on live stream everyday, my goal is to push vibe coding to the next level PPS - CNVS is a lifetime license becuase you DO NOT need another subscription in your life.

Max Blade

29,860 görüntüleme • 2 ay önce

THIS DEVELOPER CONNECTED 8 NVIDIA DGX SPARKS INTO ONE CLUSTER - AND RAN AN 800GB MODEL THAT MADE HIM 10X MORE PRODUCTIVE 21:47 he says it straight - "this is a terabyte of VRAM - we ran Quen 3.5, 800GB on disk, a model that doesn't even fit on a single Mac Studio - 24 tokens per second - I'd say that's a win" 8 Sparks connected through a $1,300 switch via RDMA over Ethernet - each node adding 128GB of memory into one unified pool of 1TB started with one Spark at 3 tokens per second - every added node doubled the speed - and eight together deliver 24 tokens on a model that physically cannot run anywhere else Kimi K2 at 600GB loaded in 15 minutes, 115GB per node, 13 tokens per second - a model that simply cannot run on anything smaller Claude helped configure the entire cluster - SSH mesh across all 8 machines, network config, jumbo frames, QSFP port speeds - all from one terminal most people rent cloud compute for models this size at $2,000+/month - he built the cluster once and now every token costs 20x less

THIS DEVELOPER CONNECTED 8 NVIDIA DGX SPARKS INTO ONE CLUSTER - AND RAN AN 800GB MODEL THAT MADE HIM 10X MORE PRODUCTIVE 21:47 he says it straight - "this is a terabyte of VRAM - we ran Quen 3.5, 800GB on disk, a model that doesn't even fit on a single Mac Studio - 24 tokens per second - I'd say that's a win" 8 Sparks connected through a $1,300 switch via RDMA over Ethernet - each node adding 128GB of memory into one unified pool of 1TB started with one Spark at 3 tokens per second - every added node doubled the speed - and eight together deliver 24 tokens on a model that physically cannot run anywhere else Kimi K2 at 600GB loaded in 15 minutes, 115GB per node, 13 tokens per second - a model that simply cannot run on anything smaller Claude helped configure the entire cluster - SSH mesh across all 8 machines, network config, jumbo frames, QSFP port speeds - all from one terminal most people rent cloud compute for models this size at $2,000+/month - he built the cluster once and now every token costs 20x less

Noisy

186,592 görüntüleme • 3 ay önce

OpenAI and Anthropic this week: GPT-Red, Fable 5 plan changes, and free Claude for teachers (Week 29, 2026) OpenAI introduced GPT-Red, an internal automated red teamer trained through adversarial self-play to find prompt injection vulnerabilities at scale Training against it made GPT-5.6 their most robust model against prompt injections to date And there's a hidden "GPT-RED // Invader Patrol" game in the article OpenAI also published GPT-Live usage limits, brought ChatGPT back to WhatsApp in the European Economic Area, rolled out a new unified search in ChatGPT across chats, projects, images, and documents, raised the custom instructions limit from 1,500 to 5,000 characters, and updated the ChatGPT desktop app with a clearer Chat and Work layout, unified Recents, Projects, and cloud sync ChatGPT Finances got Apple Card and Savings support On the publishing side, OpenAI shared articles on managing AI investments in the agentic era, why teens deserve access to safe AI, state and federal AI safety action, and Sarah Friar's useful intelligence per dollar scorecard Beyond the official channels, Bloomberg reported OpenAI's first device will be a movable screenless smart speaker, and The New York Times reported a Kalshi partnership showing World Cup odds in ChatGPT search Work Louder launched the Codex Micro keypad built for Codex, OpenAI merch is back in a new Supply Co. shop, and I spotted a new private equity and investment management community in the works Anthropic made Claude Fable 5 standard in all Max and Team Premium plans at 50% of limits starting July 20, with a one-time $100 credit for Pro and Team Standard, after extending Fable 5 access on paid plans through July 19 Claude Code weekly limits stay 50% higher through August 19 Anthropic also introduced Claude for Teachers with free premium Claude access for verified K-12 educators in the US, committed 10 million Canadian dollars to Canadian AI research, and published a Canada Economic Index country brief Artifacts in Claude Code now support public sharing, multiplayer editing, and MCP connectors, plus creation via Claude Tag Claude Code got /code-review effort levels up to ultra, and HIPAA configuration is now self-serve for Claude organizations On the research side, Anthropic published work on Claude's values across models and languages, and four new agentic misalignment case studies

OpenAI and Anthropic this week: GPT-Red, Fable 5 plan changes, and free Claude for teachers (Week 29, 2026) OpenAI introduced GPT-Red, an internal automated red teamer trained through adversarial self-play to find prompt injection vulnerabilities at scale Training against it made GPT-5.6 their most robust model against prompt injections to date And there's a hidden "GPT-RED // Invader Patrol" game in the article OpenAI also published GPT-Live usage limits, brought ChatGPT back to WhatsApp in the European Economic Area, rolled out a new unified search in ChatGPT across chats, projects, images, and documents, raised the custom instructions limit from 1,500 to 5,000 characters, and updated the ChatGPT desktop app with a clearer Chat and Work layout, unified Recents, Projects, and cloud sync ChatGPT Finances got Apple Card and Savings support On the publishing side, OpenAI shared articles on managing AI investments in the agentic era, why teens deserve access to safe AI, state and federal AI safety action, and Sarah Friar's useful intelligence per dollar scorecard Beyond the official channels, Bloomberg reported OpenAI's first device will be a movable screenless smart speaker, and The New York Times reported a Kalshi partnership showing World Cup odds in ChatGPT search Work Louder launched the Codex Micro keypad built for Codex, OpenAI merch is back in a new Supply Co. shop, and I spotted a new private equity and investment management community in the works Anthropic made Claude Fable 5 standard in all Max and Team Premium plans at 50% of limits starting July 20, with a one-time $100 credit for Pro and Team Standard, after extending Fable 5 access on paid plans through July 19 Claude Code weekly limits stay 50% higher through August 19 Anthropic also introduced Claude for Teachers with free premium Claude access for verified K-12 educators in the US, committed 10 million Canadian dollars to Canadian AI research, and published a Canada Economic Index country brief Artifacts in Claude Code now support public sharing, multiplayer editing, and MCP connectors, plus creation via Claude Tag Claude Code got /code-review effort levels up to ultra, and HIPAA configuration is now self-serve for Claude organizations On the research side, Anthropic published work on Claude's values across models and languages, and four new agentic misalignment case studies

Tibor Blaho

13,137 görüntüleme • 2 ay önce

You can now try Llama 3.1 405B for free (link below)! This is the largest open-source model out there, and for the first time, an open model is competitive with closed models. This time around, Meta did something new: Llama 3.1 has a license that allows developers to use it to enhance other models. For the first time, you can distill Llama 3.1 405B's capabilities into a smaller, more practical model for your use case. First, here is the link where you can play with Llama 3.1 for free: The model is hosted in Tune Studio, an end-to-end platform for developing applications using Large Language Models. They are sponsoring this post. Take a look at the attached video. It will show you how you can fine-tune a simple model using Llama 3.1 without leaving the platform: 1. You can create an empty dataset 2. Use the playground to generate and record interactions with Llama 3.1 3. Modify the dataset directly using the playground 4. Export the data and fine-tune a smaller model Fast and easy! As long as you have a web browser, you can start experimenting with fine-tuning and Llama 3.1. That's all it takes!

You can now try Llama 3.1 405B for free (link below)! This is the largest open-source model out there, and for the first time, an open model is competitive with closed models. This time around, Meta did something new: Llama 3.1 has a license that allows developers to use it to enhance other models. For the first time, you can distill Llama 3.1 405B's capabilities into a smaller, more practical model for your use case. First, here is the link where you can play with Llama 3.1 for free: The model is hosted in Tune Studio, an end-to-end platform for developing applications using Large Language Models. They are sponsoring this post. Take a look at the attached video. It will show you how you can fine-tune a simple model using Llama 3.1 without leaving the platform: 1. You can create an empty dataset 2. Use the playground to generate and record interactions with Llama 3.1 3. Modify the dataset directly using the playground 4. Export the data and fine-tune a smaller model Fast and easy! As long as you have a web browser, you can start experimenting with fine-tuning and Llama 3.1. That's all it takes!

Santiago

55,609 görüntüleme • 2 yıl önce

OpenClaw has 186K GitHub stars and 1.5M compromised API keys. I needed a secure alternative. So, I built it with n8n and Claude Opus 4.6. It can already: - Reply to your Telegram messages - Access selected folders from your laptop - Access Gmail, Drive, Notion, Linear, etc. - Install new local tools in a sandbox - Run autonomously for hours - Create multiple subagents - Learn from experience - Wake up regularly But, unlike OpenClaw, it: - Can't access your API keys - Can't modify its environment - Can't access folders you haven't shared - Can't access tools you haven't approved - Must get your confirmation, e.g., when sending emails These aren’t prompt instructions. They’re hard architectural boundaries — Docker isolation, mounted folder permissions, n8n’s tool approval system. Key components: ✅ The VPS on Hostinger hosts n8n and a sandbox container. Agents can also connect to my laptop's sandbox via a Claudeflare tunnel + Desktop Commander MCP. ✅ The Manager agent is the brain. It plans, decides, delegates, and talks to the user. It never touches files. It never runs scripts. It works entirely from executor summaries. ✅ The Executor agents are the hands. Each receives a task (what to do + why it matters), decides how to execute it, and reports back. They can install new tools and execute code only in their dedicated sandboxes. ✅ Data Tables in n8n store both memories and sessions — no external database, no vector store, no infrastructure. Just rows in a table. Turns out, that's enough. Two memory types: - Manager memory: user preferences, facts, corrections, relationship, skills, context - Executor memory: what tools are installed, what’s broken, workarounds ✅ Sessions are short-term state for multi-step tasks. Original request, plan, assumptions, and what happened so far. When the Manager loops with fresh context, the session is all it gets. That's a Ralph Wiggum loop. I've been using it for 5 days. And already can't imagine not having it on my phone. What's next: - Heartbeat via Cron (a scheduled prompt) - Civic Nexus governance + MCPs - Supermemory integration - WhatsApp as an additional surface - Hardening The architecture supports all of it. OpenClaw proved people want personal AI agents. It also proved that 'just trust the prompt' isn't a security model. Docker isolation, mounted folder permissions, tool approval — none of this is new technology. It's just discipline. You can easily do this even with n8n — no coding required. --- Want to try it or read more? More, what I learned, and a setup guide: productcompass[.]pm

OpenClaw has 186K GitHub stars and 1.5M compromised API keys. I needed a secure alternative. So, I built it with n8n and Claude Opus 4.6. It can already: - Reply to your Telegram messages - Access selected folders from your laptop - Access Gmail, Drive, Notion, Linear, etc. - Install new local tools in a sandbox - Run autonomously for hours - Create multiple subagents - Learn from experience - Wake up regularly But, unlike OpenClaw, it: - Can't access your API keys - Can't modify its environment - Can't access folders you haven't shared - Can't access tools you haven't approved - Must get your confirmation, e.g., when sending emails These aren’t prompt instructions. They’re hard architectural boundaries — Docker isolation, mounted folder permissions, n8n’s tool approval system. Key components: ✅ The VPS on Hostinger hosts n8n and a sandbox container. Agents can also connect to my laptop's sandbox via a Claudeflare tunnel + Desktop Commander MCP. ✅ The Manager agent is the brain. It plans, decides, delegates, and talks to the user. It never touches files. It never runs scripts. It works entirely from executor summaries. ✅ The Executor agents are the hands. Each receives a task (what to do + why it matters), decides how to execute it, and reports back. They can install new tools and execute code only in their dedicated sandboxes. ✅ Data Tables in n8n store both memories and sessions — no external database, no vector store, no infrastructure. Just rows in a table. Turns out, that's enough. Two memory types: - Manager memory: user preferences, facts, corrections, relationship, skills, context - Executor memory: what tools are installed, what’s broken, workarounds ✅ Sessions are short-term state for multi-step tasks. Original request, plan, assumptions, and what happened so far. When the Manager loops with fresh context, the session is all it gets. That's a Ralph Wiggum loop. I've been using it for 5 days. And already can't imagine not having it on my phone. What's next: - Heartbeat via Cron (a scheduled prompt) - Civic Nexus governance + MCPs - Supermemory integration - WhatsApp as an additional surface - Hardening The architecture supports all of it. OpenClaw proved people want personal AI agents. It also proved that 'just trust the prompt' isn't a security model. Docker isolation, mounted folder permissions, tool approval — none of this is new technology. It's just discipline. You can easily do this even with n8n — no coding required. --- Want to try it or read more? More, what I learned, and a setup guide: productcompass[.]pm

Paweł Huryn

54,038 görüntüleme • 7 ay önce