<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Shell on Devops Monk</title><link>https://devops-monk.com/tags/shell/</link><description>Recent content in Shell on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 26 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/shell/index.xml" rel="self" type="application/rss+xml"/><item><title>You Don't Need a Framework to Build an AI Assistant</title><link>https://devops-monk.com/2026/04/build-ai-assistant-without-framework/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/2026/04/build-ai-assistant-without-framework/</guid><description>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&amp;rsquo;s headless mode (-p flag) plus a markdown file for personality plus cron scheduling is a complete AI assistant stack.</description></item></channel></rss>