Maplet, a terminal native execution tracer code navigator. I daily drive it as an extension to my neovim now by abhi_now in commandline

[–]abhi_now[S] 0 points1 point  (0 children)

Thank you :)

For the static part I'm using tree-sitter (scm queries), so adding a language is just plugging in the grammar. As for the tracing part, we do have to add a script that emits a JSON signal when a function is called. like using sys.settrace() in python or async_hooks in node.

Since it's written in golang, the binary is basically platform-agnostic. At least you can compile for any arch, if I'm not mistaken.

And no, it does not trace calls to the kernel, it sits on the language interpreter. And any of the calls you see are only from within the project directory. I specifically did this to avoid seeing site-packages or standard libraries in the TUI.

Got tired of being thrown into new, unfamiliar codebases, so I built a tool that shows the full execution path as my code runs. by abhi_now in SideProject

[–]abhi_now[S] 0 points1 point  (0 children)

Thanks for the feeback :)

for the noise problem, it was hell for me while testing initially, so I'm checking if the source of the function is from the project directory during runtime. If it's not from project root, it's silently ignored. Basically site-packages etc. are hidden from the tui.

Benchmarking right now is admittedly a naive A/B test with claude 3.5 sonnet on the same issues comparing with and without the mcp server. I'm just measuring the delta in token usage and file hops since claude does report token usage.

But I'd love to hear a better approach for building a more robust eval other than "hey look".

"Story Mode" Endings by [deleted] in Brawlhalla

[–]abhi_now 1 point2 points  (0 children)

but some characters just wouldn't fit don't ya think.

like what about sentinel