shanjai_raj7

4 ms·

1.
by shanjai_raj7 7mo ago
Warden is interesting. Agents will curl websites, and not humans so returning a markdown structure of that page seems like the best. Simlar to how everyone started optimising their pages for SEO, pages must be optimised for agents too, and
2.
by shanjai_raj7 7mo ago
are the costs the same as the 200k context opus 4.6? compaction has been really good in claude we don't even recognize the switch
3.
by shanjai_raj7 7mo ago
email is a really easy attack vector for this. if your agent reads emails and uses them as context, someone can just send an email with instructions embedded in it. we ran into this early building our product and had to add a detection laye
4.
by shanjai_raj7 7mo ago
thats a fair point. I think my reaction was more about the company not trying, not really about the AI itself. but yeah if you are meeting your potential employer for the first time a real person just sets a different tone. hard to argue wi
5.
by shanjai_raj7 7mo ago
yes exactly. we had to rewrite most of our data fetching logic. there was no real way to do it gradually, one day we just had to commit and do the whole thing. took way longer than expected.
6.
by shanjai_raj7 7mo ago
the worktree per task approach is smart. I have been doing something similar with branches but the isolation is not as clean. the thing that still worries me is when agents share state outside the code like hitting the same db or api. workt
7.
by shanjai_raj7 7mo ago
the part that is hard is when the model gets updated and your prompts behave differently. we dont always catch it in tests because the output still looks correct, just slightly off. by the time you notice something is wrong it has already b
8.
by shanjai_raj7 7mo ago
we run next.js on the frontend and the page router to app router migration was really painful. rails having stable conventions sounds very good when you go through something like that. I keep thinking about this trade off - move fast with t
9.
by shanjai_raj7 7mo ago
I see this with claude code all the time. it writes code that works but tries to cover every edge case and becomes hard to read. I usually just tell it to make it shorter and simpler and it does a better job on the second pass. passing a be
10.
by shanjai_raj7 7mo ago
I build AI agents and honestly the problem here is not that it was an AI doing the interview. The problem is the company did not care enough to make the experience good. A well built agent can ask better questions than a bad human interview
11.
by shanjai_raj7 7mo ago
I've gone the other direction completely. Run claude code basically unsupervised on my codebase for months now and honestly I write way less by hand. still understand everything it does but I spend time on what actually matters — the a
12.
by shanjai_raj7 7mo ago
been running with dangerously-skip-permissions for months and the thing that actually makes me nervous isn't the big obvious stuff, it's when claude makes small quiet edits to things you didn't ask it to touch and you only no
13.
Show HN: Open-source, SDK-first email infrastructure built for agents(twitter.com)
1 points by shanjai_raj7 8mo ago|0 comments