Omarchy Runs Your Coding Agent With the Safety Off
Omarchy's launcher gives every coding agent a skip-approval flag by default. The attack surface a security lead inherits, and what Omarchy gets right.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Writing · Tag
26 posts on AI tools. Or browse the full writing index →
Omarchy's launcher gives every coding agent a skip-approval flag by default. The attack surface a security lead inherits, and what Omarchy gets right.
Omarchy's own AGENTS.md, skills, and a design doc reviewed by two other vendors' agents — read from the quattro branch, not the README.
Compression toward machine-preferred notation isn't a future bet. It's already landing in context formats, agent protocols, and the files your harness reads.
Four Elixir options for schema-validated LLM output, scored on maintenance, provider coverage, retry behavior, and escape hatches.
José Valim's case for Elixir as a coding-agent harness holds up on the runtime. The tax is the ecosystem around it — sandboxing, plugins, and SDKs.
A restructure log: what broke in the AIOS v1 tree at multi-scope scale, why identity-first beats type-first, and what shipped in v2.
Model names scattered across every repo's config rot the day a model gets deprecated or repriced. One git-versioned markdown table fixes it for good.
The exact hooks in this repo settings.json: a .env guard, a draft-post warn, mix format, a JSON validator, and the real matcher and exit-code mechanics.
Where TDD with Claude Code actually holds up in an Elixir/Phoenix codebase — ExUnit async, mix precommit, Ecto.Multi idempotency — and where it breaks.
The CLAUDE.md entries that actually earned their place on a real project — mistake-driven rules, not a speculative template you copy once and forget.
My team's $200 AI coding seats consume $1,800–$3,500 of API-priced tokens a month. The 10–17x arbitrage nobody prices in, and how to budget for it.
I open-sourced the AI operating system I run daily: a git-versioned markdown vault, cross-repo wiring, and a nightly ingest loop. Fifteen minutes to set up.
Your accumulated agent memory is a bet on one vendor's format. Build a portable, git-versioned knowledge layer any agent can read instead.
The Claude Code plugins that earn a permanent slot in my stack, sorted by what they actually change — my process, my domain expertise, or just friction.
An homage to Peter Welch's Programming Sucks, updated for agents: a genius intern with amnesia, hallucinated packages, and a closet that eats your auth layer.
A markdown knowledge base your AI agent reads and maintains — the three-layer architecture, the ingest/query/lint loop, and the rules that stop it rotting.
A CLAUDE.md isn't config — it's executable tribal knowledge. The onboarding doc you never wrote for humans, finally read by something that acts on it.
Eight failure patterns I see running AI coding agents daily — the confident wrong answers, the lost context, and the bugs they reliably ship.
The Hex packages I install on day one of a new Elixir project in 2026 — what each earns its place doing, and the ones I dropped along the way.
A Tencent benchmark across 20 languages found Elixir at the top of LLM code-completion rates — Claude Opus 4 hit 80.3% on Elixir vs 74.9% on C#. The reasons aren't an accident; they're the same boring properties that have always made Elixir pleasant, now compounded by AI.
Most engineers prompt Claude one sentence at a time. Anthropic's own engineers don't — they prompt skills. Four rules from their recent talks, with the operator nuance the talks left out.
Fifty prompts I use to ship production AI features, debug distributed systems, and write docs that don't rot. Code review, debugging, refactoring, system design, and PR-quality writing — with five full examples.
Ruflo (formerly Claude Flow) is a hive-mind orchestration layer for Claude Code and friends. 45,000+ GitHub stars, 700,000+ npm downloads, three queen-types...
The 46 Claude Code tools worth installing in 2026, and the ones to skip, sorted by category with a recommended starter stack at the end.
Most engineers using Claude Code see a 10–15% speedup. The teams seeing 40–55% aren't typing faster — they're sequencing work differently. The four modes I use AI in, what to never delegate, and how to get a skeptical team across the line.
A walkthrough of how I run 4–7 agent sessions in parallel through a normal engineering day. Morning background tasks, mid-morning pair programming, afternoon reviews, end-of-day ops. The interaction modes that work, the handoff protocol, and the trap that makes most agent workflows produce slop.