41–50 of 70 posts
Nice. Ask your slopservant to make a video, please.
https://news.ycombinator.com/item?id=48608570#48618398
"Clanker" is considered a slur
https://news.ycombinator.com/item?id=47598511#47601098
how clanker took off
Other than being aesthetically pleasing (which it doubtlessly is), what's the use case for this?
A lot of people want a use case. One I think might be cool is some kind of spatial/represented comparison: let's see how two different models interact with the codebase (for the same problem), what they touched, and what they did. Or the same model, but averaged across 100 runs, so we can see how much variance there really is per task. Something along those lines sounds interesting to me.
A lot of people want a use case. One I think might be cool is some kind of spatial/represented comparison: let's see how two different models interact with the codebase (for the same problem), what they touched, and what they did. Or the same model, but averaged across 100 runs, so we can see how much variance there really is per task. Something along those lines sounds interesting to me.
I think the issue is, on the surface this is very much a "watch this non-deterministic actvity" but I can see the value in it. This is self promotional but I am working on a "Brain" (https://github.com/gitsense/pi-brains) for the Pi (https://github.com/earendil-works/pi) coding agent and I can actually see this being quite useful to quickly tell if you did make an agent smarter or not.
There is obviously different ways you can do this, but I can see being able to quickly visualize changes based on additional knowledge/constraints can be quite useful.
A lot of people want a use case. One I think might be cool is some kind of spatial/represented comparison: let's see how two different models interact with the codebase (for the same problem), what they touched, and what they did. Or the same model, but averaged across 100 runs, so we can see how much variance there really is per task. Something along those lines sounds interesting to me.
> A lot of people want a use case. I think the issue is, on the surface this is very much a "watch this non-deterministic actvity" but I can see the value in it. This is self promotional but I am working on a "Brain" ( https://github.com/gitsense/pi-brains ) for the Pi ( https://github.com/earendil-works/pi ) coding agent and I can actually see this being quite useful to quickly tell if you did make an agent smarter…
Earlier quoted context omitted.
> A lot of people want a use case. I think the issue is, on the surface this is very much a "watch this non-deterministic actvity" but I can see the value in it. This is self promotional but I am working on a "Brain" ( https://github.com/gitsense/pi-brains ) for the Pi ( https://github.com/earendil-works/pi ) coding agent and I can actually see this being quite useful to quickly tell if you did make an agent smarter…
I'd advise you to put a video demo at the top of your repo, similar to OP, to convince or interest me.
https://github.com/gitsense/gsc-rules-demos
One of the rules shows how you can inject information when you know an agent wants to read a certain file. So if you have skills related to a certain file/directory, you can inject the information when you need to.
So using the OPs visualization tool, if you find the agent wandering you could create a new rule to guide the agent and compare it with and with guidance.
Well done creating A Cool Thing!
* https://en.wikipedia.org/wiki/Chord_diagram_(information_vis...
* https://en.wikipedia.org/wiki/Treemapping
When it comes to coding sessions my problems are memory and inter-agent communication, for which I'm using https://ctx.rs/, and tracking, for which I'm testing https://usegitai.com/
I do not see what there is to be gained from replaying a session.