7 posts on Claude Code.
Claude Code and Codex are strong at non-coding work: research, writing, files, reports and recurring ops. How to set up a folder for it, what each tool does differently on schedules and approvals, where the DIY setup costs you, and how to run it in Kavela.
How to run Claude Code on a schedule: cron with the headless CLI, GitHub Actions, and Claude Code's own schedulers. The pitfalls (expired logins, a sleeping laptop, runs nobody sees) and how a calendar of routines running in the cloud on your Claude plan avoids them.
What Claude Code orchestration means in practice: subagents, parallel sessions in git worktrees, and a lead agent that splits the work. Where it breaks (handoffs, ownership, approvals, sessions that die) and how to run it with a manager agent on your own Claude plan.
Yes, Claude can manage other agents. How the manager and worker pattern works, how to prompt a lead agent to delegate well, the three ways it fails (the manager does the work, context gets lost, nobody reviews) and how to run workers on your own Claude plan.
How to manage tasks with Claude Code: one task per piece of work, each with an owner, a due date, a status and a deliverable. Set it up by hand with markdown task files, see where that stops working, and how a calendar of tasks filed by a manager agent fixes it.
Managing many Claude Code or Codex sessions means tab sprawl, runs that die when the laptop sleeps, lost context and constant checking. Practical fixes (names, worktrees, tmux, notes, notifications) and the structural one: sessions as tasks on a calendar.
How to run a UGC farm with Claude: audience research, hook writing, script variants in your brand voice, reviewing generated videos against reference clips, and a weekly content plan, with your approval before anything posts. Plus how to run it in Kavela on your Claude plan.