notnotrishi

I built it because I was tired of typing out bug reports or constant prompting or wrestling with screenshots. Now I just circle what's broken and get a detailed ticket. Works with any app on macOS. Would love feedback on the approach and what integrations you'd want next. Thanks!

not that i know, but that's something we def. need

agree!

wdym by 'screenshots of interviews'? like coding interview questions?

interesting, will check it out

curious what you meant by a knowledge system. thanks

haven't tried aider. looks interesting

yes, o1 def. seems to have a deeper 'understanding'

thanks!

> with Claude if you start having extremely long conversations I have noticed it allowing certain bugs it had already fixed to be reintroduced at much later times

i think this is a result of its inability to handle long contexts well?

My notes:

- Sonnet 3.5 seems good with code generation and o1-preview seems good with debugging

- Sonnet 3.5 struggles with long contexts whereas o1-preview seems good at identifying interdependencies between files in code repo in answering complex questions

- Breaking the problem into small steps seems to yield better results with Sonnet

- I’m using primarily in Cursor/GH Copilot and with Python