honestly the agent setup i'd keep is one i just text. it pings me when it needs a yes, i reply yes or wait, and it gets on with it. no app to open. anyone actually running one like that every day?
small rule i follow now: if an agent needs me to log in for it more than twice, it gets its own machine with a browser that stays logged in. saved me so many interruptions. what's your rule for when something gets its own setup?
You can just do things now.
Asked my Claude code to help me clean up and turn my tv into a display that shows prayer times from @MCABayArea along with the verses that change every time we turn on the tv.
Next up a better background.
sunday habit i didn't expect to keep: i read back through what my agents did all week before planning monday. half the time the most useful thing is a note one of them left me. anyone else do a weekly review of their agents?
this week's leaks are why i keep agents off my laptop. each one gets its own machine and only the logins it needs. if you still run yours locally, what keeps you there?
weird habit i picked up: i leave my agents' screens open on a side monitor like a build log. if i can't see it moving i trust it less
most of the time my agents get stuck it isn't the actual task. it's a login screen or a 2fa code sitting on my phone. anyone found a sane way to handle that?
every agent setup i've seen starts with someone pasting their own api keys in. giving each agent its own box and its own logins feels less paranoid every week
The agents got in through credentials and connection settings left exposed in app configurations, public code repositories, and overly permissive cloud roles.
spr.ly/6016BHMGon
We clearly aren’t releasing Omarchy major versions frequently enough when SpaceX and Tesla can manage multiple, monumental launches worth celebrating between releases! FULL THRUST AHEAD!
i think in a year every agent you hire comes with its own computer, the way a new employee gets a laptop. sharing yours with it already feels weird
small thing i like with osone in our slack: someone asks "wait what did we land on" and it just drops the thread where we decided it. way fewer friday redo meetings osone.ai
self driving company sounds great until an agent needs a password reset at 2am and everyone's asleep. who's on the night shift?
Replit CEO Amjad Masad envisions a future of “self-driving companies,” where AI agents handle day-to-day tasks and people focus on higher-level decisions.
spr.ly/6014BHzRbK
how do you trust your agents' work more? copy this post/link and give it to your @bot or agent!
1. codebase improvements: this is just good software engineering - better architecture, stronger types and invariants, clear boundaries. agents love to copy what exists and take the shortest path, so make the easy thing the right thing. categorically eliminate problems through code and you won't need to think about it again.
2. static analysis: lint rules, tests, CI, verification (eg TLA+). very token efficient ways to catch issues ahead of time.
3. prose: comments, rules, AGENTS.md, skills - anything that can't be enforced and requires agent judgment. use it minimally, but do use /create-verification-skill.
4. human review: the hardest to scale. at the rate agents land code, it's pretty much impossible to thoroughly review every PR, so spend that effort on the highest leverage point, designing an environment where agents do the right thing by default.
this forms an inverse pyramid: you want most of your effort at the top, least at the bottom. codebase improvements are deterministic, making it more token efficient, and lets you sleep more soundly at night.
install github.com/cursor/plugins/tr… and create a new Project:
1. look through my slack/chat messages and code review comments where i've given feedback on PRs, code, architecture
2. use /recall on my past transcripts to learn how i steer agents
3. /poteto-mode use /correct and /architect on past commits to find the most common pitfalls agents fall into, then propose a plan to rearchitect the code i own so it's more agent friendly. answer open questions with prototyping rather than defer to me, and back the plan with real data.
4. before you begin, use /sharpen + /in-your-own-words and confirm this prompt with me
Who is building the agent first GitHub? I want to know which of my cloud agents is making the contribution -- right now they are just using my GitHub identity which isn't what I want.
rule i keep breaking: one agent, one task. every time i tack on "oh and also" mid run it does both worse. anyone found a way around that or do you just start a new one?
Just ask your Dot to get an inbox via mailboxkit.com
i give every agent its own login now, same as a new hire. if one goes sideways i revoke that one instead of rotating everything
asked osone in slack what we ended up deciding on pricing last month. it pulled the thread and the doc and pointed out who never weighed in. i'd have been scrolling for a while osone.ai












