7 posts on Ai Productivity.
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.
What can I automate with Claude, Claude Code or Codex? Use a simple $20 test for picking the right job, six recurring jobs that pass it, what not to automate, the honest cost of running them yourself, and a prompt to start one in Kavela.
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.
Running several AI agents brings file collisions, orphaned tasks, duplicate work, lost context and silent waits. How to coordinate multiple AI agents: one coordinator, one owner per task, isolated workspaces, shared context, one approvals queue and a visible schedule.
What a tool needs to orchestrate AI agents: one view of all work, clear ownership, schedules, approvals, logs and deliverables, and agents that keep running with your editor closed. How an editor, terminal multiplexing and a calendar workspace compare.
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 be more efficient with your AI use: write briefs with a goal and done criteria, batch and schedule recurring work, keep context in one place, review deliverables instead of watching runs, and get full use from the Claude or Codex plan you already pay for.