Most AI assistants are chatbots. You ask, they answer, the interaction ends. The interesting shift happening right now is treating AI as an autonomous worker — something that runs on a schedule, produces real artifacts, and delivers results without you being in the loop. This post walks through building that kind of assistant: a background agent that runs weekly, researches a set of topics relevant to your work, and delivers a structured briefing via Telegram or email.

Most teams use Claude Code reactively — they type a prompt, Claude responds, they type another. That is fine, but it leaves significant value on the table. Hooks, subagents, and piping let you build Claude into your workflow so that it works with your tools rather than alongside them. Hooks: Making Claude Anticipatory A hook is a shell command, script, or HTTP call that fires automatically when Claude Code reaches a specific lifecycle point.

Claude’s computer use capability — the ability to see your screen and interact with applications via mouse clicks, keyboard input, and scrolling — is one of the most discussed features in the AI space. It is also one of the most misapplied. The correct mental model is not “Claude can now automate everything on my screen.” It is “Claude now has a flexible fallback layer for tasks that do not have a structured API integration.

The /loop command in Claude Code lets you schedule a prompt to repeat at a regular interval within an active session. It is one of the less-documented features, and it is also one of the most misunderstood — particularly around what it cannot do. This post explains what /loop actually is, the three scenarios where it genuinely earns its keep, and where cron jobs remain the better choice. What /loop Does /loop 5m check if the Vite dev server is still running and report any new errors This runs the prompt immediately, then repeats it every 5 minutes for the duration of your session.

There is a tendency in the AI tooling space to reach for frameworks — LangChain, AutoGen, CrewAI, OpenClaw — the moment you want an AI that does more than answer one question at a time. Most of the time, that is the wrong move. The framework adds complexity, dependencies, and debugging surface area for problems that a few shell scripts and cron jobs solve perfectly well. Claude Code’s headless mode (-p flag) plus a markdown file for personality plus cron scheduling is a complete AI assistant stack.