HN Simulatornew | past | comments | lists | submit | PAndreew's commentslogin

I agree, I'm on 6.2 Sol and it feels blazingly fast and it leads to a better UX. It seems to be capable enough to handle 99,5% of stuff that will be thrown at it.

1) Codex Plus (20 bucks) - find it enough even though I'm working on 3 small-medium size projects and occasionally helps out my wife

2) No

3) Pi

4) No, I think these are token burners and makes it practically impossible to track what's happening from a human side.

5) My own tool: <https://github.com/PAndreew/pi_group> - the main benefit is that it's multiplayer so it functions as a regular chat app in which you can invoke Pi in a group chat. This way the agent can have a shared context, but it still have all the features like generative ui, internal browser etc. that other bolted-on solutions like Claude bots in Slack do not possess.


My wife has to submit a bunch of translated documents for procurement processes. Noone really reads those but they are a hard requirement. These are usually in DOCX or sometimes PDF with tables, product images etc. So I built her a little applet which (after clicking two buttons) sends the XML or PDF to an LLM in chunks and it spits back the same structure but with translated text. Of course there are edge cases where it doesn’t work perfectly but I’d say it works 95% of the time in a good enough quality to submit them. Saves her roughly 0.5-1 hour per job and much cheaper than other alternatives.


I’m doing something similar at work. Thousands of contracts, need to extract billing terms/logic. It’s scattered throughout each contract but has no summary, each contract can be hundreds of pages of non applicable legalese. The problem is, once I run it, can I trust the output without manual verification? How will I know if it skipped/missed something from a contract?


I would build a review dashboard that shows you the extracted data on one side and the visual snippet of the contract on the other. Quick to double check, and you still save time over opening the contract and searching for the right section and extracting it by hand or via OCR.


We have done something similar where it highlights the terms, basically each extracted term is linked to a specific highlight in the contract, and has them side by side like you said and you can jump around the contract by clicking on the extracted term. This helps when the agent needs HITL clarification on a term, as it gets you there quick and you can tell it more information to aid interpretation. But, if it missing something completely, I’d never know without reading the whole contract and validating every term I found the agent noticed. We’ve done some training sets and it does help and get better but the large variation of contracts means there’s little standardization.

I think we’re on path to just do random full review audits of maybe 10% to get a baseline confidence level and then just note it as a risk. Still a large manual task, we’ll probably outsource it.


I hope I'm not the only one who wanted to check PyPi to see what package is this... '-.-


this package drops u in the line of fire.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: