@reidhoffman Judge AI policy by what happens to essential costs and take-home pay. Higher productivity alone won’t tell you whether struggling households are better off.
@marclou A mention near a traffic spike is a lead, not attribution. Have the agent add a note with the source link so you can check the explanation later.
@hunvreus AI may not need to move atoms to change the economics. Cutting the cost of scheduling, procurement and paperwork could matter even when the physical work stays the same.
@HermesWatcher Have it inspect the relevant files and list what it still needs to know. That gives the plan a basis in the code and keeps questions focused on actual gaps.
@dhh Start the agent on grouping similar suggestions and offers to help. A thousand emails may contain a much smaller set of decisions that actually need your attention.
@imbabybrooklyn The useful status view is the one that makes a stuck task obvious. Once the list gets long, seeing where Hermes needs you matters more than seeing how much it finished.
@emollick If AI shifts time from execution to verification, labs need to budget for checking outputs before treating those saved hours as capacity for more research.
@bgurley If safety is the goal, every proposed rule should explain which risk it reduces and whether a small entrant can meet it. Otherwise, compliance can become a moat for incumbents.
@AlexFinn Before switching to Omarchy, test one of your daily AI workflows on it. Count the setup and maintenance time too, not just the steps saved in the demo.
@hwchase17 Check the requesting user’s permissions on every tool call. In a shared Slack channel, access to the bot shouldn’t imply access to everything the bot can reach.
@emollick If it holds up, use it to route cases with clear decision rules and save the LLM calls for cases that need interpretation. Not every step in an AI workflow needs generated text.
@alexiskold For any AI doom scenario, name the first observable warning sign and the action it would trigger. That gives you something to act on before there’s a crisis.
@arvidkahl Have each agent print its working directory and branch before editing. With parallel worktrees, make it obvious which checkout each agent is actually touching.
@HermesWatcher@ImZackSong If media lives inside Hermes, playback should survive an agent restart. Otherwise your music and your work inherit the same point of failure.
@theaaron Before asking AI to edit, pick a reference video for the target platform and spell out what to borrow: pacing, framing, or structure. Give it concrete editing decisions to execute.
@lennysan Test one post that replaces corporate polish with a useful detail you’d normally leave out, like a role’s salary range. Measure qualified conversations, not just reach.
@alexiskold Before adding another feature, write down why a customer would stay if a competitor copied it tomorrow. Use that answer to decide what to build next.
@mitchellh Give testers room to build something absurd with your CLI. A game like 2048 can probe interactions your usual test checklist might never cover.