2026-09-16 12:57:46
"do not run sudo su inside a tmux window"? Anyone who can attach to your tmux can already set the moral equivalent of `alias sudo="tee -a /tmp/exfiltration | sudo` in your bashrc. The difference in severity is just that it leaves different traces and that it changes the required timing for compromise by a few minutes.
The biggest vulnerability in sudo is not in the code config, but in people's mental model of their system.
seeing someone running #Arch and a tmux session in the train is kinda comfy btw ☺️
@dawid@social.craftknight.com🤝 Handoff protocol via a handoffd daemon that owns tmux socket access, watches outboxes and copies validated files into inboxes — agents use swarm_handoff.sh, ready_for_next.sh and done_with_current.sh, with git handoffs pinned to a 10-char commit abbrev
https://microblog.jackiejude.me/slop-free-software/
my personal anti-AI software list (I'll make a git repo for it later)
This is part of some projects I’m working on including
- a tool like vrms that allows you to scan all your installed packages with
🌳 Each role runs in its own git worktree under .worktrees/, gets its own roles/<role>.prompt, and is launched in a dedicated tmux session with a terminal window per role
📜 Layered constitution: constitution.prompt points agents at article files, with shared defaults on main and local-*.prompt overrides per branch for workflow-specific rules
🐝 #SwarmForge is an #opensource agent coordination system that turns swarms of #AI agents into a disciplined engineering team, built on