Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ramoz
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
151.
▲
by
ramoz
7mo ago
I follow a very similar workflow, with manual human review of plans and continuous feedback loops with the plan iterations See me in action here. It's a quick demo: https://youtu.be/a_AT7cEN_9I
152.
▲
by
ramoz
7mo ago
There was a complete verification. This entire thread provides context around what I originally published - which I wouldn't recommend recreating
153.
▲
by
ramoz
7mo ago
Thanks for the transparency. Sorry for the noise. I think I'd be okay with a smaller, more narrative-detailed plan - not so much about verbosity, more about me understanding what is about to happen & why. There hadn't been muc
154.
▲
by
ramoz
7mo ago
This stemmed from me asking Claude itself why it was writing such _weird_ plans with no detail (just a bunch of projected code changes). Claude stated: in its system prompt, it had strict instructions to provide no context or details. Keep
155.
▲
by
ramoz
7mo ago
I understand. Thank you for sharing. I didn't uncover all of this until Claude told me its specific system instructions when I asked it to conduct introspection. I'll revise the blog so that I don't encourage anybody else to
156.
▲
by
ramoz
7mo ago
I apologize for doing this - and I agree. I will revise
157.
▲
by
ramoz
7mo ago
I understand. Just with AI, I don't think the behavior should change so drastically. Which I understand is paradoxical because we enjoy it when it can 10x or 1000x our workflow. I think responsible AI includes more transparency and cap
158.
▲
Please do not A/B test my workflow
(backnotprop.com)
169 points
by
ramoz
7mo ago
|
210 comments
159.
▲
by
ramoz
7mo ago
I'll try posting again today, just because this is an active thing that I'm trying to get fixed.
160.
▲
Anthropic, Do Not A/B Test My Workflow
(backnotprop.com)
23 points
by
ramoz
7mo ago
|
2 comments
161.
▲
Show HN: Tiny macOS app that adds a facecam bubble to screen recordings
(github.com)
5 points
by
ramoz
7mo ago
|
0 comments
162.
▲
If Claude Code is performing poorly, you might be in an A/B test
(twitter.com)
5 points
by
ramoz
7mo ago
|
0 comments
163.
▲
by
ramoz
7mo ago
There's a known bug in the VS Code native extension - hooks dont work. Somewhere in their sea of issues on GitHub, it's in there.
164.
▲
by
ramoz
7mo ago
Well, your best bet is some type of hook that can just reject ExitPlanMode and remind Claude that he's to stay in plan. You can use `PreToolUse` for ExitPlanMode or `PermissionRequest` for ExitPlanMode. Just vibe code a little toggle t
165.
▲
by
ramoz
7mo ago
The OpenCode plan experience has been pretty bad (the community has accepted this, at least on Discord). The community's adopted a handful of plugins to make the experience better, and also guardrail when the agent switches versus does
166.
▲
by
ramoz
7mo ago
Great job with the tool.
167.
▲
by
ramoz
7mo ago
If the data includes every contractor that competed for an award & lost, that is data is typically not public.
168.
▲
by
ramoz
7mo ago
The first one is literally a well-known massive corporation
169.
▲
by
ramoz
7mo ago
It is all public.
170.
▲
by
ramoz
7mo ago
It's missing data for sure - at least on the awarded side. (Which is easy to vet because it's all public) https://www.usaspending.gov/search?hash=181b0ab9a8cc9f30fbed...
171.
▲
by
ramoz
7mo ago
The deterministic context system is intuitive and well-designed. That said, there's more to consider, particularly around user intent and broader information flow. I created the hooks feature request while building something similar[1]
172.
▲
Ask HN: What are you using to mitigate prompt injection?
6 points
by
ramoz
7mo ago
|
4 comments
173.
▲
by
ramoz
7mo ago
Level4 is most interesting to me right now. And I would say we as an industry are still figuring out the right ergonomics and UX around these four things. I spend a great deal of my time planning and assessing/reviewing through various
174.
▲
by
ramoz
7mo ago
I don't think anybody at Meta involved in the aquisition must be an avid OpenClaw user or developer. Moltbook was more of a meme - agents mostly orchestrated by users in the background. Not something with motion like OpenClaw itself (w
175.
▲
Show HN: Manual code review and feedback loop for agents
(twitter.com)
4 points
by
ramoz
7mo ago
|
0 comments
176.
▲
Show HN: Git Worktrees Simplified
(github.com)
2 points
by
ramoz
7mo ago
|
0 comments
177.
▲
Simplifying Git Worktrees
(backnotprop.com)
3 points
by
ramoz
7mo ago
|
0 comments
178.
▲
by
ramoz
7mo ago
Skills is the right abstraction.
179.
▲
by
ramoz
7mo ago
Side project - plan mode and code review annotations for coding agents (ui that integrates via hooks): https://github.com/backnotprop/plannotator Main gig: Trusted agents. We just shipped hardware based signing to web
180.
▲
by
ramoz
7mo ago
Where are we at with SOTA or reliable prompt injection detection mechanisms?
More ›