Top
Best
New

Posted by cosmtrek 14 hours ago

Show HN: Mindwalk – Replay coding-agent sessions on a 3D map of your codebase(github.com)
138 points | 61 commentspage 2
smw 5 hours ago|
Any license for it? I think technically we can't even run it legally at the moment?
cosmtrek 5 hours ago|
MIT. I've added it. Have fun!
smw 2 hours ago||
Many thanks!
geeewhy 10 hours ago||
this is cool! i started tracking file changes across sessions with file hunk method on a binlog.. to see hot paths, or do partial reverts where files werent committed across my sessions. not for visual, but operational for the harness i use. approach lets you see the whole rollups on a period of days or minutes. think there are many use cases where you can run a side agent to check things / progress analyze risky areas as you go etc etcs .. all file change lookups are 3-5ms. script here: https://github.com/geeewhy/haicue-brew/tree/main/scripts

i wonder if i would be able to visualize with mindwalk

rcarmo 12 hours ago||
Very nice, but needs pi.dev / rcarmo/piclaw support :)
cosmtrek 11 hours ago|
Thanks, added to my backlog~
nokeya 10 hours ago||
First thought after reading “3D map of your codebase” was that now we will be able to code in Johnny Mnemonic style :D
Treegarden 11 hours ago||
I tested it, history feature is per agent session, a cumulative history of all my agents would be nice.
pshc 11 hours ago||
Very glad to see this, I've been dreaming about spatial representations for code for a long time.
bakwan44 11 hours ago||
That's great but im not sure what the use cases are. Did you have something in mind when building this to help the conception process ? I dont feel like i need to know what the agent did, never opened the session json. But there could be gold in there perhaps.
cosmtrek 10 hours ago||
My original motivation is to compare the task-solving ability of LLMs by visualizing the agent's trajectory. This offers an alternative way to inspect the capabilities of LLMs and agent systems.
freakynit 10 hours ago||
This can help you evaluate agentic capabilites of various llm's. How they explore codebase.
aviperl 8 hours ago||
Heads up, I get a 404 on the 30 sec demo link.
altmanaltman 11 hours ago||
This reminds me of that community epsiode where they get the VR system and the dean has to walk through a maze, climb up several things so that they can go to a filing cabinet and then retrive a file. Yes, its cool to see and watch but it seems to be adding more friction than reducing it. Like who is going to spend that much time watching what their agents did when there are far quicker and efficient ways of scanning through changes and organizing code with better ergonomics?
lukan 10 hours ago|
"when there are far quicker and efficient ways of scanning through changes and organizing code with better ergonomics?"

Like what?

altmanaltman 10 hours ago||
Standard CLI version control tools like git diff, git log, or any built-in IDE diff viewer. Scrolling through a text summary of changes is inherently faster and more ergonomic than generating a 3D spatial visualization and watching an agent physically navigate through it.
lukan 10 hours ago|||
(Though I disagree, not sure why this comment was flagged? vouched for it)

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.

anigbrowl 2 hours ago||||
Counterpoint: it's not

I absolutely hate using diff view except when I'm debugging. Reading (or even skimming) 2 text files at once demands a lot of concentration. Now following activity in visual displays like these also takes concentration, and the process can certainly be refined further, but they can help you get a quick overview of what's going on in the same way as a profiling graph.

liangleoup 10 hours ago|||
[dead]
soupspaces 11 hours ago|
Sort of like gource?
cosmtrek 10 hours ago|
Wow, it's my first time learning it. The visualization seems similar.
iamflimflam1 9 hours ago||
gource seems to be on of those tools that people forget about. I don’t know if it’s the name or just simply that it’s the kind of thing you run once and think “that’s nice - what do I do with it?”. It’s not something you run regularly so it slowly disappears from memory.
More comments...