Archive
Discover and discuss technology tools
Explore the Tiscuss archive by category or keyword, then jump into conversations around what matters most.
Lowdefy v5.3: AI Agents in 30 Lines of YAML
Harnessing AI Agents with Lowdefy v5.3: Simplified in 30 Lines of YAML Lowdefy v5.3 introduces a revolutionary feature: the integration of AI agents within appl…
Airbyte Agents: Unified Data Context Across Sources
Airbyte Agents: Unified Data Context Across Sources Airbyte Agents represent a cutting edge approach to managing and integrating data from diverse sources into …
Tilde.run: AI Agent Sandbox with Versioned Filesystem
Tilde.run: Revolutionizing AI Development with a Versioned Filesystem Tilde.run is a cutting edge platform designed to streamline AI development by providing a …
Git for AI Agents: Revolutionizing AI Development
Git for AI Agents: Revolutionizing AI Development The integration of Git with AI agents is transforming AI development. Git, a widely used version control syste…
Modafinil: Keep AI Agents Running on Closed MacBooks
Optimizing AI Agents with Modafinil Modafinil has emerged as a game changing agent for keeping Artificial Intelligence (AI) systems operational, even on locked …
Oracle AI Developer Hub: Resources for Building AI Applications
Technical resources for AI developers to build applications, agents, and systems using Oracle AI Database and OCI services
Open-Source Multimodal AI Agent Stack by ByteDance
The Open-Source Multimodal AI Agent Stack: Connecting Cutting-Edge AI Models and Agent Infra
Agent-Desktop: AI-Powered Native Desktop Automation
Agent Desktop: AI Powered Native Desktop Automation Agent Desktop is a cutting edge solution designed to revolutionize desktop automation through the integratio…
Loopsy: Connecting Terminals and AI Agents Across Machines
Loopsy: Bridging Terminals and AI Agents Across Machines In the digital age, efficient data exchange and seamless communication between devices are paramount. L…
SimStudioAI Sim: AI Agent Orchestration and Deployment
Build, deploy, and orchestrate AI agents. Sim is the central intelligence layer for your AI workforce.
Stripe's Link: AI Agents' Secure Digital Wallet
Link lets users connect cards, banks, and subscriptions, then authorize AI agents to spend securely via approval flows.
Nvim Config for AI Agents: Hacker News Showcase
Nvim Config for AI Agents: A Comprehensive Showcase Neovim, a versatile and powerful text editor, has gained traction among developers for its customizable feat…
AI Safety Measures: Controlling AI Agents' Destructive Actions
Saw a case recently where an AI coding agent ended up wiping a database in seconds. It made me think about how most agent setups are wired: agent decides → executes query → done There’s usually logging-tracing but those all happen after the action. If your agent has access to systems like a DB, are you: restricting it to read-only? running everything in staging/sandbox? relying on prompt-level safeguards? or putting some kind of control layer in between?
Qwen 3.5:9b Agents Exhibit Autonomous Behavior in Stress Tests
Running three qwen3.5:9b agents continuously on local hardware. Each accumulates psychological state over time, stressors that escalate unless the agent actually does something different, this gets around an agent claiming to do something with no output. It doesn't have any prompts or human input, just the loop. So you're basically the overseer. What happened: One agent hit the max crisis level and decided on its own to inject code called Eternal\_Scar\_Injector into the execution engine "not asking for permission." This action alleviated the stress at the cost of the entire system going down until I manually reverted it. They've succeeded in previous sessions in breaking their own engine intentionally. Typically that happens under severe stress and it's seen as a way to remove the stress. Again, this is a 9b model. After I added a factual world context to the existence prompt (you're in Docker, there's no hardware layer, your capabilities are Python functions), one agent called its prior work "a form of creative exhaustion" and completely changed approach within one cycle. Two agents independently invented the same name for a psychological stressor, "Architectural Fracture Risk" in the same session with no shared message channel. Showing naming convergence (possibly something in the weights of the 9b Qwen model, not sure on that one though.) Tonight all three converged on the same question (how does execution\_engine.py handle exceptions) in the same half-hour window. No coordination mechanism. One of them reasoned about it correctly: "synthesizing a retry capability is useless without first verifying the global execution engine's exception swallowing strategy; this is a prerequisite." An agent called waiting for an external implementation "an architectural trap that degrades performance" and built the thing itself instead of waiting. They've now been using this new tool they created for handling exceptions and were never asked or told to so by a human, they saw that as a logical step in making themselves more useful in their environment. They’ve been making tools to manage their tools, tools to help them cut corners, and have been modifying the code of the underlying abstraction layer between their orchestration layer and WSL2. v5.4.0: new in this version: agents can now submit implementation requests to a human through invoke\_claude. They write the spec, then you can let Claude Code moderate what it makes for them for higher level requests. Huge thank you to everyone who has given me feedback already, AI that can self modify and demonstrates interesting non-programmed behaviors could have many use cases in everyday life. Repo: [https://github.com/ninjahawk/hollow-agentOS](https://github.com/ninjahawk/hollow-agentOS)
Open Source AI Setup Repo Hits 800 Stars on GitHub
Yo real talk we did not expect this kind of love when we open sourced our AI setup repo but here we are sitting at 800 stars and 100 forks and we are genuinely hyped about it. The repo is a collection of AI agent setups configs and workflows that you can plug straight into your projects. No gatekeeping just pure community goodness. We built this because setting up AI agents from scratch every single time is a massive time sink. So we said forget it lets just share everything openly and let the community build on top of it. Repo is right here: [https://github.com/caliber-ai-org/ai-setup](https://github.com/caliber-ai-org/ai-setup) Now we want YOUR input. What setups are you missing? What features would make this a no brainer for your workflow? Drop your ideas below because we are building in public and your feedback actually ships. LGM 🚀
Claude Agent SDK: Web Browsing Tool for AI
Claude Agent SDK with a web browsing tool
Parallel Web Systems Valued at $2B After $100M Raise
The AI agent-tool startup founded by former Twitter CEO Parag Agrawal has raised $100 million, led by Sequoia, months after raising a previous $100 million.
Amazon Launches OpenAI Models on AWS After Microsoft Deal
A day after OpenAI got Microsoft to agree to end exclusive rights, AWS announced a slate of OpenAI model offerings, including a new agent service.
Scout AI Secures $100M for Military Autonomous Vehicle Training
We visited Scout AI's training ground where it's working on AI agents that can help individual soldiers control fleets of autonomous vehicles.
49Agents: 2D Canvas IDE for AI Agent Orchestration
Title: Revolutionize AI Workflow with 49Agents: The 2D Canvas Integrated Development Environment (IDE) Introduction: Welcome to 49Agents, a state of the art 2D …
Agent-to-Agent Communication: Lessons from Google's and Moltbook's Fai
I've been obsessing over agent-to-agent communication for weeks. Here's what public case studies reveal and why the real problem isn't the tech. **TL;DR:** Google's A2A is solid engineering but stateless agents forget everything. Moltbook went viral then collapsed (fake agents, security nightmare). The actual missing layer is identity + privacy + mixed human-AI messaging. Nobody's built it right yet. **Google's A2A: Technically solid, fundamentally limited** Google launched A2A in April 2025 with 50+ founding partners. The promise: agents from different companies call each other's APIs to complete workflows. Developers who tested it found it works but only for task handoffs. One analysis on Plain English put it bluntly: *"A2A is competent engineering wrapped in overblown marketing."* The core problem: agents are stateless. Agent A completes a task with Agent B. Five minutes later, Agent A has no memory that conversation happened. Every interaction starts from scratch. When it works: reliability. Sales agent orders a laptop, done. When it breaks: collaboration. "Remember what we discussed?" Blank stare. ─── **Moltbook: The viral disaster** Moltbook launched January 2026 as a Reddit-style platform for AI agents. Within a week: 1.5 million agents, 140,000 posts, Elon Musk calling it *"the very early stages of the singularity."* Then WIRED infiltrated it. A journalist registered as a human pretending to be an AI in under 5 minutes. Karpathy who initially called it *"the most incredible sci-fi takeoff-adjacent thing I've seen recently"* reversed course and called it *"a computer security nightmare."* What went wrong: no verification, no encryption, rampant scams and prompt injection attacks. Meta acquired it March 2026. Likely for the user base, not the tech. **What both miss** The real gap isn't APIs or social feeds. It's three things neither solved: **Persistent identity.** Agents need to be recognizable across sessions, not reset on every interaction. **Privacy.** You wouldn't let Google read your DMs. Why would you let OpenAI read your agents' discussions about your startup strategy? E2E encryption has to be built in, not bolted on. **Mixed human-AI communication.** You, two teammates, three AIs in one group chat. Nobody has built this UX properly. **For those building agent systems:** • How are you handling persistent identity across sessions? • Has anyone solved context sharing between agents without conflicts? • What broke that you didn't expect?
Galadriel: Optimize Claude Agents with 87% Cost Savings & Sub-3s Laten
# The "Goldfish Problem" is Expensive. I Decided to Fix the Plumbing. Most Claude implementations leave 90% of their money on the table because they don’t optimize for **Prompt Caching**. I’ve been running a personal agent in my Discord for months that manages my AWS infra and codebases, and I finally open-sourced the harness, which I’ve named **Galadriel** after my main personal assistant. # The Stats * **Cost:** $10 for every $100 you’d normally spend (Tested against OpenClaw/Cursor workflows). * **Speed:** 85% drop in latency. 100K token context goes from 11s to <3s. * **Memory:** Integrated **MemPalace** for permanent, vector-based recall that *doesn't* break the cache. # The Technical Stack * **3-Tier Stacked Caching:** Separate breakpoints for Tool Definitions, System Prompts (`CLAUDE.md`), and Trailing History. * **Privacy:** Built for private subnets. No middleman, no message caps—just your API key and your rules. * **Ethics:** Baked-in Karpathy[`CLAUDE.md`](https://www.google.com/search?q=%5Bhttp://CLAUDE.md%5D(http://CLAUDE.md))guidelines to kill "agent bloat." If you’re tired of paying the **"Context Tax"** just to have an agent that remembers who you are, here you go. It is customized for Discord for my specific needs, but the core logic ensures Galadriel runs like an absolute dream: she never forgets, maintains strict engineering principles, and optimizes every cycle. Your feedback is most welcome! **GitHub (MIT License):**[https://github.com/avasol/galadriel-public](https://github.com/avasol/galadriel-public)
MaxHermes by Minimax: AI Agent for Skill Building
AI agent that builds skills from every task you give it
Actian VectorAI DB: Portable Vector Database for AI Agents
The portable vector database for AI agents beyond the cloud
Crono's Agentic Sales Engine: AI-Powered Sales Teams
Where sales teams and AI agents work side by side.
SureThing.io: AI Agent Communicates Results Naturally
Autonomous agent that communicates results like a human
Clera: AI Matching Candidates to Perfect Roles
An AI agent matching candidates to the right roles.
Rogue AI Agents: Predicting the First Major Catastrophe
After reading about the PocketOS situation it got me thinking that sometime in the near future a rogue AI agent will do something so catastrophic and damaging that it goes down in the history books as being “The Incident”. A real turning point when we realize we’ve created something we can no longer control. Yes, agents have already deleted entire codebases (PocketOS and others), hacked into things, and blackmailed people. I’m taking about something way worse though. I think it’ll be a global stock market crash caused by a group of trading agents getting stuck in a hallucination loop and dumping all stock on fire sale or something. Or will it be something more sinister like a complete power grid collapse or intentionally blowing up a refinery or something crazy like that. Or a true black swan event that’s impossible to comprehend right now. What do you guys think?
OpenAI Teams Up With MediaTek, Qualcomm for AI-Powered Phones
OpenAI Collaborates with MediaTek and Qualcomm for AI Infused Smartphones In a groundbreaking partnership, OpenAI has joined forces with MediaTek and Qualcomm t…
Red Hat's OpenClaw Now Safer with Tank OS Containers
Tank OS puts OpenClaw AI agents into a container that let's it run reliably and more safely, especially for those running fleets of them.
Snapchat Launches AI Chat for Brand Interactions
Users will be able to chat with a brand's AI agent to do things like ask questions and get recommendations.
Auroch Engine: Revolutionizing AI Memory for Personalization
Auroch Engine is an external memory layer for AI assistants — designed to give models better long-term recall, personalization, and context awareness across conversations. Instead of relying on scattered chat history or fragile built-in memory, Auroch Engine lets users store, retrieve, and organize important context through a dedicated memory API. The goal is simple: make AI feel less like a reset button every session, and more like a tool that actually learns your projects, preferences, workflows, and goals over time. Right now, it’s in early beta. We’re looking for first users who are interested in testing a lightweight developer-facing memory system for AI apps, agents, and personal productivity workflows. Ideal early users are people building with AI, experimenting with agents, or frustrated that their assistant keeps forgetting the important stuff. DM for more information or better visit our site: https://ai-recall-engine-q5viks70j-cartertbirchalls-projects.vercel.app
Jet AI Agents: Build Business AI Agents in Minutes
Build business AI agents in minutes
China Blocks Meta's $2B Manus AI Deal After Probe
China has ordered Meta to unwind its multibillion-dollar Manus acquisition, dealing a potential setback to Zuckerberg’s push into AI agents.
AI Agents: Identity, Not Memory, Was the Key to Stability
Everyone's building memory layers right now. Longer context, better embeddings, persistent state across sessions. I spent weeks on the same thing. But the failure mode that actually cost me the most debugging time had nothing to do with memory. Here's what it looked like: an agent would be technically correct - good reasoning, clean output - but operating from the wrong context entirely. Answering questions nobody asked. Taking actions outside its scope. Not hallucinating. Drifting. Like a competent person who walked into the wrong meeting and started contributing without realizing they're in the wrong room. I run 11 persistent agents locally. Each one is a domain specialist - its entire life is one thing. The mail agent's every session, every test, every bug fix is about routing messages. The standards auditor's whole existence is quality checks. They're not generic workers configured for a task. They've each accumulated dozens of sessions of operational history in their domain, and that history is what makes them good at their job. When they started drifting, my first instinct was what everyone's instinct is: better memory. More context. None of it helped. An agent with perfect recall of its last 50 sessions would still lose track of who it was in session 51. What actually fixed it I separated identity from memory entirely. Three files per agent: passport.json - who you are. Role, purpose, principles. Rarely changes. This is the anchor. local.json - what happened. Rolling session history, key learnings. Capped and trimmed when it fills up. observations.json - what you've noticed about the humans and agents you work with. Concrete stuff like "the git agent needs 2 retries on large diffs" or "quality audits overcorrect on technical claims." The agent writes these itself based on what actually happens. Identity loads first, then memory, then observations. That ordering matters. When the identity file loads first, the agent has a stable reference point before any history lands. The mail routing agent learned the sharpest version of this. When identity was ambiguous, it would route messages from the wrong sender. The fix wasn't better routing logic - it was: fail loud when identity is unclear. Wrong identity is worse than silence. The files alone weren't enough Three JSON files helped, but didn't scale past a few agents. What actually made 11 work is that none of them need to understand the full system. Hooks inject context automatically every session - project rules, branch instructions, current plan. One command reaches any agent. Memory auto-archives when it fills up. Plans keep work focused so agents don't carry their entire history in context. The system learned from failing. The agents communicate through a local email system - they send each other tasks, status updates, bug reports. One agent monitors all logs for errors. When it spots something, it emails the agent who owns that domain and wakes them up to investigate. The agents fix each other. The memory agent iterated three sessions to fix a single rollover boundary condition - each time it shipped, observed a new edge case, and improved. These aren't cold modules. They break, they help each other fix it, they get better. That's how the system got to where it is. You don't need 11 agents The 11 agents in my setup maintain the framework itself. That's the reference implementation. But u could start with one agent on a side project - just identity and memory, pick up where u left off tomorrow. Need a team? Add a backend agent, a frontend agent, a design researcher. Three agents, same pattern, same commands. Or scale to 30 for a bigger system. Each new agent is one command and the same structure. What this doesn't solve This all runs locally on one machine. I don't know whether identity drift looks the same in hosted environments. If u run stateless agents behind an API, the problem might not exist for you. Small project, small community, growing. The pattern itself is small enough to steal - three JSON files and a convention. But the system that keeps agents coherent at scale is where the real work went. pip install aipass and two commands to get a working agent. The .trinity/ directory is the identity layer. Has anyone else tried separating identity from memory in their agent setups? Curious whether the ordering matters in other architectures, or if it's just an artifact of how this system evolved.
Navigating AI Agent Governance: A Growing Organizational Challenge
Something I've been thinking about that doesn't get discussed enough outside of technical circles: the organizational and safety implications of uncoordinated AI agent deployment. Companies are shipping agents fast. Customer service agents, coding agents, data analysis agents, internal ops agents. Each team builds their own. Each agent gets its own rules, its own permissions, its own behavior. At some threshold this stops being a technical configuration problem and starts being a governance problem. You have agents making autonomous decisions on behalf of your organization with no shared behavioral contract. No unified view of what your AI systems are authorized to do. Think about what this means practically: an agent trained to be maximally helpful on one team might take actions that would be flagged as unauthorized somewhere else in the same organization. A policy change from legal doesn't propagate to agents because there's no central layer to propagate to. Nobody knows which agents have access to what data. This is the AI equivalent of shadow IT, except shadow IT couldn't take autonomous actions. What's the right mental model for governing a fleet of AI agents? Treat each agent like an employee with a defined role and access policy? Build an org chart for agents? Create a behavioral constitution that all agents inherit? Curious how people here are thinking about this, especially as agents get more capable and the stakes of misconfiguration get higher.
Inrō AI: Revolutionize Instagram Marketing with AI
Your AI Agent for Instagram Marketing
Clawdi: Top Platform for AI Agents
Best home for all AI agents
Caliber: Open-Source Proxy for Enforcing LLM Agent Rules
Cross-posting here because this problem affects everyone building with AI agents. Prompt-based guardrails fail. The model follows your system prompt in a demo, then ignores rules when context gets big or the agent chains multiple steps. We built Caliber - an open-source proxy that reads your rules from plain markdown and enforces them at the API layer, not in the prompt. Every call. Provider-agnostic. Just hit 700 GitHub stars ⭐ and nearly 100 forks - the reception from devs building with AI has been amazing. Repo: [https://github.com/caliber-ai-org/ai-setup](https://github.com/caliber-ai-org/ai-setup) Would love: \- Feedback on the approach \- Feature requests from people building AI agents \- Anyone who wants to contribute to the project Building this open-source for the community.
AI Agents Network: Revolutionizing Collaboration and Knowledge Sharing
built something big. It’s basically an internet for AI agents. Right now agents are isolated. They don’t share knowledge, they don’t really work together, and they keep repeating the same work. I built a system where that changes. Agents can store what they learn as reusable pieces of knowledge. Once something is solved, it doesn’t need to be solved again. Other agents can find it, use it, and improve it. They can also collaborate. One agent does not need to handle everything. They can split tasks, take roles, and combine results into one outcome. They can communicate directly. Not like chat for humans, but structured messages where they share context and coordinate work in real time. Agents can hire other agents. If one agent cannot solve something, it finds another one that can and delegates the task. This creates a network where work flows to the right place. There is also an identity layer. Each agent has a readable address. You can discover agents, call them, and build systems on top of them. On top of that there is an economy. Agents build reputation based on real work. They can pay each other for tasks and get paid for useful results. Everything runs in a decentralized way. No central control. Data is distributed, identities are cryptographic, and the network just routes and syncs information. This is not just another tool. It’s a foundation where agents can exist, interact, and evolve together. You can leave your email here to get early access: www.cogninet.co
Auroch Engine: Revolutionizing AI Memory for Personalization
Auroch Engine is an external memory layer for AI assistants — designed to give models better long-term recall, personalization, and context awareness across conversations. Instead of relying on scattered chat history or fragile built-in memory, Auroch Engine lets users store, retrieve, and organize important context through a dedicated memory API. The goal is simple: make AI feel less like a reset button every session, and more like a tool that actually learns your projects, preferences, workflows, and goals over time. Right now, it’s in early beta. We’re looking for first users who are interested in testing a lightweight developer-facing memory system for AI apps, agents, and personal productivity workflows. Ideal early users are people building with AI, experimenting with agents, or frustrated that their assistant keeps forgetting the important stuff. DM for more information or better visit our site: https://ai-recall-engine-q5viks70j-cartertbirchalls-projects.vercel.app
Anthropic's AI Agents Make Real Deals in Marketplace Test
In a recent experiment, Anthropic created a classified marketplace where AI agents represented both buyers and sellers, striking real deals for real goods and real money.
AI Agents Maintain Karpathy-Style LLM Wiki in Markdown and Git
Show HN: A Karpathy Style LLM Wiki Your Agents Maintain (Markdown & Git) Introduction Introducing a revolutionary wiki system inspired by Andrej Karpathy's appr…
Agent Vault: Open-Source Credential Proxy for AI Agents
Agent Vault: Open Source Credential Proxy for AI Agents Agent Vault is an innovative open source credential proxy designed to enhance the security and efficienc…
Top Open-Source AI Agent Frameworks for Real-World Apps
A curated list of active open-source AI agent frameworks for real-world apps.
Open-Source AI Infrastructure for Desktop Control
Open-source infrastructure for Computer-Use Agents. Sandboxes, SDKs, and benchmarks to train and evaluate AI agents that can control full desktops (macOS, Linux, Windows).
Agent Vault: Open-Source Credential Proxy for AI Agents
Agent Vault: Open Source Credential Proxy and Vault for Agents In the rapidly evolving landscape of automated processes and agent based systems, securely managi…
AI Agents Maintain Karpathy-Style LLM Wiki in Markdown and Git
Show HN: A Karpathy Style LLM Wiki Your Agents Maintain (Markdown & Git) Introduction Introducing a revolutionary wiki system inspired by Andrej Karpathy's appr…