Joel Hooks co-founded egghead.io and builds tools and platforms for developer educators. His current work spans Badass Courses, the Course Builder ecosystem, and JoelClaw, a personal system of durable agent workflows.[1][2]
Start with JoelClaw CLI →
Career
Hooks’s developer-education work includes egghead.io and the platforms supporting courses such as Total TypeScript, AI Hero, and Epic AI. Badass describes its Course Builder framework as a technical implementation informed by years of producing developer courses. The work combines software with the process of helping an expert turn knowledge into exercises, lessons, and a sustainable product. In his 2018 interview, Hooks described an earlier career in 3D modeling and animation before moving into software and co-founding egghead.[1][2][5]
Contributions
Credentials with a shorter life
agent-secrets provides local credential storage and time-limited leases for agents. Its daemon tracks leases, supports revocation, writes an audit log, and offers an emergency killswitch. An agent can request a credential for a specific task or execute one command with temporary access. The repository credits Alex Hillman’s approach as inspiration. The practical purpose is to make credential access scoped and revocable rather than giving every agent an undifferentiated set of long-lived secrets.[4]
A personal agent system
Hooks’s JoelClaw project connects durable functions, a messaging gateway, and agent memory with reusable skills. His profile places it alongside tools for meeting notes, PDFs, diagrams, and task management, giving his agent-workflow ideas concrete commands and services that people can inspect and agents can operate.[1]
Ideas
In his CLI design essay, Hooks argues for structured responses with machine-readable results, actionable errors, and typed next steps. A response can include the exact run ID or a list of permitted status values, so an agent need not infer a command from free-form terminal text. For long-running activity, the essay uses one JSON object per line to stream progress and ends with a standard result envelope. The aim is to make a command-line tool navigable from the information it returns.[3]
Tools, writing & talks
Tools
Start here
JoelClaw CLIjoelclaw.comAn essay on structured command responses, typed next actions, bounded output, and streaming progress.
Start with the response-envelope examples, then compare one command in a tool you maintain. Familiarity with JSON and command-line interfaces is enough to understand the design argument.
Author.[3]Original source- agent-secrets
github.comA local credential manager with encrypted storage, agent leases, audit logs, and revocation controls.
Repository owner; credits prior inspiration.[4]Original source