One thing that drives me nuts with coding agents is when they finish and claim to be done, without anything to back that up.
And Kujo Spec was built to cure that frustration.
It lets you give the work clear requirements and acceptance criteria up front, so there's something to check against when your agent finishes
Point your agent at the docs and have them set it up
https://t.co/iAgQbwfRFu
> Your agent says the job is done.
Did it pass the tests? Produce the right output? Meet the requirements?
Eval lets you define checks and get repeatable pass/fail results for the work your agents produce.
You can stop taking their word for it.
https://t.co/JURBls3lyk
Just released: RepoRadar v0.5.0 ๐
- Added agent-friendly CLI reviews, JSON reports, and diagnostics.
- Added persistent hidden repositories with restore controls.
- Fixed overflowing detail buttons and long branch labels; added the Tabler chevron.
- Resolved 15 hardening findings covering scans, backups, imports, API security, metadata, and activity history.
Use RepoRadar to keep every local repo in view, so unfinished work doesn't slip through the cracks.
https://t.co/Vi5OMY9nh1
The Kujo ecosystem provides a lot of accountability for agentic workflows, but the language itself does a lot of the heavy lifting ๐ช
Native AI record/replay, cassettes, and deterministic request hashing mean you can reproduce model responses, debug failures, and run tests without paying for the same inference over and over.
Built into the language in order to provide your AI-native software development with everything it needs to succeed.
https://t.co/ZhxQ9ULr70
Accountability for agentic workflows looks like this.
If you haven't tried Kujo yet, you're missing one of the greatest opportunities of 2027 ... you gotta be thinking about your future right now ๐ซก
From start to finish, Kujo has you covered for all of your AI-native software development.
Check it out ๐
Picture it: An agent can say a task is finished while missing half the requirements ๐ซฃ
Spec gives the work an explicit contract and acceptance criteria before the first change.
You can check the result against what was actually requested.
Learn more:
https://t.co/vAvo9OaJb8
Thank you to those of you who reached out already. Exciting times ahead ๐ซก
You can't stop this train. Best thing to do now is get in early while theres still time.
[email protected]
If you want to be taken serious, you have to put in the effort.
If not, what's the point?
Kujo is open to investors, and I used the Kujo Presentations tool to build a proper deck for it.
Kujo lang -> Kujo SSG -> Kujo Presentstions -> You.
https://t.co/DpwSbjLRKN
I tested 100 contributors one at a time and concurrently.
The old way took 11m 36s while Source's concurrent batch took 2m 6s
That's about 5.5ร faster, and i haven't even truly started working on performance focused gains yet ๐ช
With this release, i tested 250 concurrent agent processes across 10 repos.
All edits were retained through submission, combined verification, and promotion ๐ฅ
I also ran 100 agents concurrently on a single repo and it handled that fine as well.
Next tests will be 250 on one repo, then 1,000 ๐ช
Its good to see decentralized AI publishing gaining traction.
Especially in places with people who seemed to be against it a year or two ago.
Growth is good ๐ซก
If you want to be taken serious, you have to put in the effort.
If not, what's the point?
Kujo is open to investors, and I used the Kujo Presentations tool to build a proper deck for it.
Kujo lang -> Kujo SSG -> Kujo Presentstions -> You.
https://t.co/DpwSbjLRKN