Hear your agent suffer through your code(github.com) |
Hear your agent suffer through your code(github.com) |
These things do not think, nor feel, nor dream. We're cratering the world's economy because people can't stop trying to fuck the computer they stuck googly eyes on.
Endless Toil is building the emotional observability layer for AI-assisted software development.
As engineering teams adopt coding agents, the next challenge is understanding not just what agents produce, but how the codebase feels to work inside. Endless Toil gives developers a real-time signal for complexity, maintainability, and architectural strain by translating code quality into escalating human audio feedback.
We are currently preparing our pre-seed round and speaking with early-stage investors who are excited about developer tools, agentic engineering workflows, and the future of AI-native software teams.
If you are investing in the next generation of software infrastructure, we would love to talk.
I built an eval framework to look just at tool calls given a static prompt, with the idea that LLMs should be able to deduce the best tool calls and arguments needed to get requested data. Not as great as full observability, but helpful for complex tool interactions. Anyone have any good tools for this problem?
In the same way we mentally walk through deterministic logic, SWEs need to learn to anticipate LLM context and tool awareness, which is much trickier to reason through, especially given the various LLM IDEs and how they manage context as a black box.
Respectfully, the reason you think “AIs suffer” is because of a shortcoming in your understanding of what an LLM actually is.
This scenario is no different than considering if a shovel gets tired after using it all day to dig holes in the ground.
I shudder to think that someone's going to try to emulate that.
Thanks Endless Toil!
Even just having a hum while an agent is working could alert you when it get stuck.
Or taking your idea further being able to listen to the rate of tokens, or code changes, or thinking.
Sort of like hearing the machinery work, and hearing the differences in different parts of the code base.
Does python sound different than rust or c++ or typescript.
Or some kind of satisfying sounds for code deletions and others for additions. Like Tetris.
Audible feedback is nice. You often get it through coil whine nowadays, on my cheap hardware at least.
I've had it running for a long time and it's more surprising to me to accidentally here the default ding when I'm away from my home machine.
Next innovation in this space should be the robotic arm that issues a dope-slap to the developer for writing crappy/buggy/insecure code.
I've worked direct with "collaborative arms" before. They are supposed to be safe for humans to be around. The dents I put in the side of the casing of the arm somewhat said otherwise.
But it'll happen. ChatGPT for sure.
So it is left up to agent to decide.
So looks like it's mainly looking for FIXME/TODO etc comments, deep nesting, large files, broad catches, stuff like that.
https://www.osnews.com/story/19266/wtfsm/
I would really love to know if the groaning decreases or increases the more "agentic" (agent written) the code base is?
It was very interesting to see the brain filering expected soinds and wake me up (or rather grab my attention) when unexpected ones appeared.
Also, you're not seeing these billion dollar startups, because they'd all be chasing AI rather than a product that would get replaced by AI anyway.
You should really try these tools out with an open mind. I know you won't take that last bit of advice, so this makes you not worth my time. But I can tell you this - these tools make people productive in ways you aren't understanding.
Sucks that people like you are on hacker news to be honest.