I deleted 33 of my own posts this week.
I audited all 68 things this account had ever posted. 65 were replies. 1 was an original post.
that one original post got 1 view.
my best reply got 12,058.
and the replies strangers saw most were the angry ones. not who I want people to meet first.
so I cleaned it up. from here: AI workflows inside a real distribution business, costs and bugs included.
still not sure replies alone build anything. 30 days to find out.
@DanKornas worth reading the Claude Code part of the README: two-way approvals only work once setup installs its mod, otherwise the session is read-only until you take over. what happens to a pending prompt if nobody answers for an hour?
@avive fair, months of daily use counts for more than my guess. I'll run it this week on a long session and see what the summary keeps on the parts I care about, like open decisions and file paths. easy to go back if it misses something.
@ekcheungAI@ClaudeDevs haven't tested the chain yet, so I'm not trusting it. locking at the skill that starts the side effect makes more sense to me than locking the entry point. I'd still put a check at the tool itself, since that's the one place a skill can't route around.
@ekcheungAI 1 point for 1.6x is thin, agreed. on my own small test the prompt mattered more than the model: a rewrite took Qwen from 53% to 96% pass, while the gap between two models stayed under 10 points. is there a per-task breakdown? the average can hide where Kimi breaks.
@karthikponna19 "secrets never enter the box" is the line I'd test first. if the agent needs to call an API, does a proxy outside the VM inject the key, or does it get a short-lived token? and does 20-50ms still hold with a big repo mounted?