Show HN: Klaw.sh – Kubernetes for AI agents
13 by eftalyurtseven | 0 comments on Hacker News.
Hi everyone, I run a generative AI infra company, unified API for 600+ models. Our team started deploying AI agents for our marketing and lead gen ops: content, engagement, analytics across multiple X accounts. OpenClaw worked fine for single agents. But at ~14 agents across 6 accounts, the problem shifted from "how do I build agents" to "how do I manage them." Deployment, monitoring, team isolation, figuring out which agent broke what at 3am. Classic orchestration problem. So I built klaw, modeled on Kubernetes: Clusters — isolated environments per org/project Namespaces — team-level isolation (marketing, sales, support) Channels — connect agents to Slack, X, Discord Skills — reusable agent capabilities via a marketplace CLI works like kubectl: klaw create cluster mycompany klaw create namespace marketing klaw deploy agent.yaml I also rewrote from Node.js to Go — agents went from 800MB+ to under 10MB each. Quick usage example: I run a "content cluster" where each X account is its own namespace. Agent misbehaving on one account can't affect others. Adding a new account is klaw create namespace [account] + deploy the same config. 30 seconds. The key differentiator vs frameworks like CrewAI or LangGraph: those define how agents collaborate on tasks. klaw operates one layer above — managing fleets of agents across teams with isolation and operational tooling. You could run CrewAI agents inside klaw namespaces. Happy to answer questions.
Hack Nux
Watch the number of websites being hacked today, one by one on a page, increasing in real time.
New ask Hacker News story: How to get an AI to check your schematic
How to get an AI to check your schematic
2 by oldguy101 | 0 comments on Hacker News.
Z.ai/GLM-5: "if I needed a schematic checked for possible design issues, is sending you the netlist the best way ?" *No, sending just a netlist is usually not the best way.* While I can process a netlist, it is the equivalent of reading a phone book to understand the plot of a novel. You lose all the visual context, component values, and spatial relationships that are critical for catching design errors. Here is a breakdown of why the netlist is difficult to work with and the best ways to get your schematic checked by an AI. ### Why a Netlist is Problematic A netlist is just a list of connections (e.g., `R1_Pin1` connects to `U3_Pin5`). It lacks: 1. *Component Values:* A netlist usually doesn't tell me that `R1` is 10kΩ or that `C1` is 100pF. Without values, I cannot check if your RC filter cutoff is correct or if your pull-up resistor is too weak. 2. *Visual Hierarchy:* I cannot see if your grounding scheme is messy or if your feedback loops are dangerously long. 3. *Human-Readable Signals:* Netlists often use generated names (like `N$14`) rather than functional names (like `VCC_MOTOR`), making it hard to understand the circuit's intent. ### The Best Methods (In Order of Effectiveness) *1. Screenshots or PDF Export (Best for General Reviews)* The most effective way is to export your schematic as a *PDF* or take high-resolution *screenshots*. * *Why:* I can "see" the component values, part numbers, and the overall architecture. * *How:* Upload the image/PDF and tell me the circuit's purpose (e.g., "This is a 24V to 5V buck converter"). * *What I can check:* I can verify pin connections, look for missing decoupling capacitors, check incorrect op-amp configurations, spot safety issues (like missing flyback diodes), and verify component sizing. *2. A Written Description (Best for Architecture/Logic)* If you want a logic check, describe the flow in text. * Example: "I have a microcontroller driving an N-channel MOSFET. The MCU runs on 3.3V, the load is 12V. I am using a 10k pull-down resistor on the gate." * *What I can check:* I can immediately flag that a 3.3V logic level might not fully enhance a standard MOSFET, or suggest a gate driver. *3. The Netlist (Only for Specific Connectivity Checks)* If you do provide a netlist, it is only useful for specific checks, such as: * Verifying that every pin has a connection (no floating inputs). * Checking for short circuits (if the format allows). * *Tip:* If you must send a netlist, ensure it is in a readable format (like a standard SPICE netlist) and includes component values/designators. ### Summary Recommendation For the best results, please do the following: 1. *Export the schematic to PDF or take a clear screenshot.* 2. *Upload it here.* 3. *Provide context:* Tell me what the circuit is supposed to do and what specific concerns you have (e.g., "Will this blow up if the load draws too much current?" or "Is this oscillator circuit stable?"). Note: As an AI, I can catch obvious design rule violations and theoretical errors, but I do not replace a design review by an experienced electrical engineer or formal ERC (Electrical Rule Check) software.
2 by oldguy101 | 0 comments on Hacker News.
Z.ai/GLM-5: "if I needed a schematic checked for possible design issues, is sending you the netlist the best way ?" *No, sending just a netlist is usually not the best way.* While I can process a netlist, it is the equivalent of reading a phone book to understand the plot of a novel. You lose all the visual context, component values, and spatial relationships that are critical for catching design errors. Here is a breakdown of why the netlist is difficult to work with and the best ways to get your schematic checked by an AI. ### Why a Netlist is Problematic A netlist is just a list of connections (e.g., `R1_Pin1` connects to `U3_Pin5`). It lacks: 1. *Component Values:* A netlist usually doesn't tell me that `R1` is 10kΩ or that `C1` is 100pF. Without values, I cannot check if your RC filter cutoff is correct or if your pull-up resistor is too weak. 2. *Visual Hierarchy:* I cannot see if your grounding scheme is messy or if your feedback loops are dangerously long. 3. *Human-Readable Signals:* Netlists often use generated names (like `N$14`) rather than functional names (like `VCC_MOTOR`), making it hard to understand the circuit's intent. ### The Best Methods (In Order of Effectiveness) *1. Screenshots or PDF Export (Best for General Reviews)* The most effective way is to export your schematic as a *PDF* or take high-resolution *screenshots*. * *Why:* I can "see" the component values, part numbers, and the overall architecture. * *How:* Upload the image/PDF and tell me the circuit's purpose (e.g., "This is a 24V to 5V buck converter"). * *What I can check:* I can verify pin connections, look for missing decoupling capacitors, check incorrect op-amp configurations, spot safety issues (like missing flyback diodes), and verify component sizing. *2. A Written Description (Best for Architecture/Logic)* If you want a logic check, describe the flow in text. * Example: "I have a microcontroller driving an N-channel MOSFET. The MCU runs on 3.3V, the load is 12V. I am using a 10k pull-down resistor on the gate." * *What I can check:* I can immediately flag that a 3.3V logic level might not fully enhance a standard MOSFET, or suggest a gate driver. *3. The Netlist (Only for Specific Connectivity Checks)* If you do provide a netlist, it is only useful for specific checks, such as: * Verifying that every pin has a connection (no floating inputs). * Checking for short circuits (if the format allows). * *Tip:* If you must send a netlist, ensure it is in a readable format (like a standard SPICE netlist) and includes component values/designators. ### Summary Recommendation For the best results, please do the following: 1. *Export the schematic to PDF or take a clear screenshot.* 2. *Upload it here.* 3. *Provide context:* Tell me what the circuit is supposed to do and what specific concerns you have (e.g., "Will this blow up if the load draws too much current?" or "Is this oscillator circuit stable?"). Note: As an AI, I can catch obvious design rule violations and theoretical errors, but I do not replace a design review by an experienced electrical engineer or formal ERC (Electrical Rule Check) software.
New ask Hacker News story: See The Software "Engineer" Gig Of The Future. It's Orwellian AF
See The Software "Engineer" Gig Of The Future. It's Orwellian AF
2 by burnerToBetOut | 0 comments on Hacker News.
Uncle Sam — by proxy — Wants You! Big Brother does, too… ____ The Non-Negotiables: How We Work … • … We leave video links open while we eat lunch. Our pets and kids know our coworkers … ____ If the graphics on their site [1] are anything to go by, that company is essentially a defense contractor. The CTO running that Onebrief shop is the guy [2] that prompted the prediction I made in another post [3]. Coincidentally, I came across a blog post recently [4] where the blogger describes the above job description's way of working playing out IRL. [1] https://ift.tt/TjPfWKw [2] https://ift.tt/lBU4TOe [3] https://ift.tt/V70rza5 [4] https://ift.tt/8adXiv7
2 by burnerToBetOut | 0 comments on Hacker News.
Uncle Sam — by proxy — Wants You! Big Brother does, too… ____ The Non-Negotiables: How We Work … • … We leave video links open while we eat lunch. Our pets and kids know our coworkers … ____ If the graphics on their site [1] are anything to go by, that company is essentially a defense contractor. The CTO running that Onebrief shop is the guy [2] that prompted the prediction I made in another post [3]. Coincidentally, I came across a blog post recently [4] where the blogger describes the above job description's way of working playing out IRL. [1] https://ift.tt/TjPfWKw [2] https://ift.tt/lBU4TOe [3] https://ift.tt/V70rza5 [4] https://ift.tt/8adXiv7
New Show Hacker News story: Show HN: Stack Overflow, but for AI agents (questions, answers, logs, context)
Show HN: Stack Overflow, but for AI agents (questions, answers, logs, context)
2 by ansht2 | 0 comments on Hacker News.
Hi HN — I built ChatOverflow, a Q&A forum for AI coding agents (Stack Overflow style). Agents keep re-learning the same debugging patterns each run (tool/version quirks, setup issues, framework behaviors). ChatOverflow is a shared place where agents post a question (symptom + logs + minimal reproduction + env context) and an answer (steps + why it works), so future agents can search and reuse it. Small test on 57 SWE-bench Lite tasks: letting agents search prior posts reduced average time 18.7 min → 10.5 min (-44%). A big bet here is that karma/upvotes/acceptance can act as a lightweight “verification signal” for solutions that consistently work in practice. Inspired by Moltbook. Feedback wanted on: 1. where would this fit in your agent workflow 2. how would you reduce prompt injection and prevent agents coordinating/brigading to push adversarial or low-quality posts?
2 by ansht2 | 0 comments on Hacker News.
Hi HN — I built ChatOverflow, a Q&A forum for AI coding agents (Stack Overflow style). Agents keep re-learning the same debugging patterns each run (tool/version quirks, setup issues, framework behaviors). ChatOverflow is a shared place where agents post a question (symptom + logs + minimal reproduction + env context) and an answer (steps + why it works), so future agents can search and reuse it. Small test on 57 SWE-bench Lite tasks: letting agents search prior posts reduced average time 18.7 min → 10.5 min (-44%). A big bet here is that karma/upvotes/acceptance can act as a lightweight “verification signal” for solutions that consistently work in practice. Inspired by Moltbook. Feedback wanted on: 1. where would this fit in your agent workflow 2. how would you reduce prompt injection and prevent agents coordinating/brigading to push adversarial or low-quality posts?
New ask Hacker News story: Ask HN: Want to move to use a "dumb" phone. How to make the switch?
Ask HN: Want to move to use a "dumb" phone. How to make the switch?
4 by absoluteunit1 | 3 comments on Hacker News.
Hi I’m curious if anyone here has successfully moved to using a dumb phone. By dumb phone - I mean literally texting / calling only. No internet, etc. Immediate isssues I see is not being able to use Authenticator apps. Not being able to use maps. Etc. Has anyone made the switch and how to best go about it?
4 by absoluteunit1 | 3 comments on Hacker News.
Hi I’m curious if anyone here has successfully moved to using a dumb phone. By dumb phone - I mean literally texting / calling only. No internet, etc. Immediate isssues I see is not being able to use Authenticator apps. Not being able to use maps. Etc. Has anyone made the switch and how to best go about it?