🛠️ All DevTools

Show HN: AgentSight – eBPF observability for AI agents, no code changes

Show HN: A desktop fly drawn to the scent of vibecode It is a fork of <a href="https:&#x2F;&#x2F;github.com&#x2F;DenisSergeevitch&#x2F;desktop-fly" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;DenisSergeevitch&#x2F;desktop-fly</a>, but with an important update.<p>Now the fly can pick up the scent of the codebase with its neurons and fly straight to the source code of your B2B AI SaaS startup. It has learned to scan its surroundings for agent markers: AGENTS.md, CLAUDE.md, .cursor&#x2F;rules, .kiro&#x2F;steering, and forty others. Anything on the screen that points to these markers becomes a source of the scent - an editor window with an open project, a line in Finder, or a desktop icon. An open project reeks the strongest, while a closed icon or nested folders give off a fainter odor.

WPD won't replace stolen Flock cameras, citing public trust

I accidentally logged phone calls to military bases

Grand jury declines to indict Ohio man charged with destroying Flock camera

The road to ACID transactions in Cassandra 6

Show HN: Lunar, a coding harness extensible with Lua Hi all! Sharing a small pet project my agents and I have been working on:<p>Lunar, a coding harness configurable and extensible via Lua scripts.<p>I&#x27;m already using Lunar to develop Lunar :) Give it a try!<p>Soon you will be able to extend it using Lua hooks.

Show HN: Argentic – An L402 Lightning toll booth for AI scraping agents

Japan tried to build an operating system for the world, the US intervened

Codex on AWS bedrock bug causing 10x charges

Framework responds to complaints that BIOS update bricks Ryzen 7040 laptops

Artificial Intelligence Policy

The Citizen Developer

Code as an Artifact

Early-life stress leaves a 'scar' inside brain cells

Show HN: Praxos – team messaging with built-in memory Hey HN! What does a regular workflow at a startup look like?<p>Probably like this:<p>&gt; One founder talks to customers<p>&gt; Another founder builds<p>&gt; A customer asks for something. The first founder explains it to the second. The second founder explains it to Claude<p>&gt; Two weeks any one of the founders asks one of the following questions:<p><pre><code> \* Why are we building it this way? \* What happened here? \* What did we promise ACME we’d do? \* How far along are we on X? </code></pre> &gt; Then you scream on the inside because you have to figure out what happened...<p>Before agents, the person who did one part of the work usually held a mental map. They could share the context with other people. Increasingly, they can’t.<p>Small teams can run far more work in parallel than ever before thanks to AI, but someone now has to connect all that context manually. The reasoning behind one product change might now be scattered across a customer call, two emails, a Slack thread, and four Claude conversations.<p>Praxos is a team messaging app.<p>It has channels, groups and threads like you’d expect. However, places where work happens—Github, harnesses, email, calls—get linked and converted into a living record of your company. This means everyone is always up to date with the latest developments.<p>Agents can join conversations and inherit the same context humans do.<p>Here are examples we’ve seen in production:<p>You talk to a customer. Later, when an engineer or coding agent works on the feature, your conversation and the customer’s information are already in context. A new engineer picks up an existing project. They have immediate access to info about who worked on what part of the code base, the deltas across changes, and a granular view of their conversations with coding agents. There’s no need to interrogate the CTO. Three weeks later, someone asks why the engineer made a certain decision about the feature. Praxos fetches the engineer’s convos, the original feature request and call logs between the founder and the engineer. Then it contextualizes the work.<p>We’re early, but the core product already works and is in use. You get messaging, search, memory and connectors. You can bring your own agents, use ours, or both.<p>A desktop app is going live next week. We’re building native calls and mobile apps, so that all the communications that go into a company’s history can happen on Praxos.<p>If you’re a 2 to 10 person team where one person is spending all day with customers while the rest of the team is shipping with Claude&#x2F;Codex, we’d love to personally onboard you.<p>Especially if you’ve already caught yourself asking “what did the customer want?” or “what’s going on with X?” last week.<p>The first 10 teams to sign up get Praxos for free for 6 months.<p>Email lucas@praxos.ai to get started!

Aaron Swartz was prosecuted for scraping, while Meta does it without consequence

GitHub, autoscaling, and the component substitution fallacy

Tidal Cycles – Live coding music with Algorithmic patterns

Show HN: Huzzah – a novel approach to coding with AI Hello everyone. I&#x27;ve been working on this experimental editor called Huzzah.<p>I&#x27;ve been working almost exclusively with coding agents since January of this year, and over the past few months I began to feel utterly exhausted by them. They&#x27;re great, but I&#x27;m finding it more and more tedious to write full sentences for every change I want. Not only that, but it seems there&#x27;s a complexity limit for codebases - beyond a certain point the agent begins confusing itself.<p>I&#x27;d like to go back to writing code, but I don&#x27;t want to go all the way back to fully manual coding. So I&#x27;ve come up with this interaction paradigm where you:<p><pre><code> 1. write pseudocode in whatever way makes the most sense to you 2. on save, the editor synchronizes your work to real source code 3. the pseudocode is persisted alongside the generated code, making your prompt effectively a stored record of intent. </code></pre> It may not work for every use case, but in my initial playthroughs I&#x27;ve found it very enjoyable.<p>Right now it&#x27;s just a proof of concept - installation instructions are here in the readme: <a href="https:&#x2F;&#x2F;github.com&#x2F;danielvaughn&#x2F;hz" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;danielvaughn&#x2F;hz</a><p>You can also watch a video of it in action here: <a href="https:&#x2F;&#x2F;x.com&#x2F;danielvaughn&#x2F;status&#x2F;2090456808431165715" rel="nofollow">https:&#x2F;&#x2F;x.com&#x2F;danielvaughn&#x2F;status&#x2F;2090456808431165715</a><p>Cheers!