DE version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
78% Positive
Analyzed from 1399 words in the discussion.
Trending Topics
#agent#https#com#file#cool#built#case#something#problem#changes

Discussion (54 Comments)Read Original on HackerNews
Well done creating A Cool Thing!
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.
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.
> It's pretty, but I can't think of anything I'd use it as a "tool" for. - https://news.ycombinator.com/item?id=21560013
Seems any time this sort of software comes up on, people can't let the use case be "this is aesthetically pleasing".
Anyways, besides that, the README does clearly state "The Problem" and "The Idea" which outlines exactly why the author built this particular project.
I asked about the use case _because_ the readme states a problem but does not offer a solution to that problem as far as I could see.
Use case is to monitor agents activity.
i wonder if i would be able to visualize with mindwalk
Like what?
If you have a big codebase, text diff is not faster to see what was done here and there, then a visual overview. I don't know about this project, but experimented with other tools of this kind and am building one myself. With text diff - you have to parse lots of text and you cannot see on one glance that, oh, these changes are in the rendering, this is DB - and here was done something with the server connection. If done right, I can immediately or very quickly see what was changed - and also decide if the agent (or human) did work in the right spots or gone off track. Now doing this right is not easy, but reading lot's of text is definitely slower then seeing, oh in this area there was a change.
according to packages: https://github.com/cosmtrek/mindwalk/blob/master/web/package...
* 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.
Thanks OP.
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