Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview
31–40 of 167 posts
Re: Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview
#32Re: Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview
#33Is there a leaderboard out there comparing harness results using the same models?
Re: Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview
#34I haven't tried it, but I'm curious why you decided to implement a whole new harness over just writing extensions in pi. From whatever I've done with pi so far, the extension api is quite extensive. Hash anchored edits, for example, can definitely be implemented in pi. Anyhow, thank you for showing us your project and will be checking it out later. Cheers!
Re: Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview
#35that said context management seem to be solving today model problems, more than being an universal property, and will probably be obsoleted a few model generations down the road, as tool obsoleted RAG context injection from question embeddings.
Re: Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview
#36Interesting. Would love a comparison to pi.dev (Not Ohmypi) How does this perform in day to day coding tasks, outside of benchmarks?
https://github.com/dirac-run/dirac#-evals README has eval of 8 tasks over 7 agents (including both pi and omp). Pi-mono costs second lowest across the 8 tasks (after Dirac) but occasionally misses produces incomplete changes. Interestingly, 2 tasks where pi missed some changes both were the tasks that benefitted from AST symbol understanding (e.g. find all instances of things that refer to this symbol and change thos…
Re: Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview
#37Earlier quoted context omitted.
Wrt LSP, it uses the default LSP mechanism of the ide provider. For AST, it uses tree-sitter WASMs (ships them with the package), and maintains queries ( https://github.com/dirac-run/dirac/tree/master/src/services/... ) To keep performance fast, it stores the symbols DB (using sqlite) in the workspace's directory and incrementally updates it based on timestamps. Then it uses this DB to resolve symbol queries
Yes I understand, but do you not have issues that it drifts out of date and confuses the agents (especially on longer running tasks)? Like even "full" Visual Studio and Resharper have issues with this. Eg, you start editing file x, 'intellisense' runs, says there are loads of errors... because you haven't finished editing yet.
Re: Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview
#38Re: Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview
#39Interesting things Dirac does: 1. Uses an optimized version of Hash-Anchored edits for file editing ( https://dirac.run/posts/hash-anchors-myers-diff-single-token ) 2. Utilizes language's AST to decide what to fetch into context, entirely avoids large code file reads 3. Batches all operations. Does large number of reads/edits simultaneously (you can see a video demo for deepseek-v4-flash here https://www.reddit.com/r…
Does that mean that it's only going to work with certain langauges for which it has parsers available?
Re: Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview
#40Interesting things Dirac does: 1. Uses an optimized version of Hash-Anchored edits for file editing ( https://dirac.run/posts/hash-anchors-myers-diff-single-token ) 2. Utilizes language's AST to decide what to fetch into context, entirely avoids large code file reads 3. Batches all operations. Does large number of reads/edits simultaneously (you can see a video demo for deepseek-v4-flash here https://www.reddit.com/r…
Congratulations, great work.