A quick build-log update for the Claude Code and OpenClaw crowd - we're closing in on a useful milestone and could use your support. Hey everyone, I'm Yusuf, co-founder at Vendo (YC S26). Berkeley honors grad at 19, Stanford MS, and now building open-source software that lets companies agentify their products: embedded agents your customers use to automate work, build views, and connect their tools. We're at 412 stars and I'm trying to push past 500 so more builders find it. If you have a GitHub account, this takes 10 seconds: open https://github.com/runvendo/vendo and hit the Star button in the top right. That's it. Live product if you want to poke at it: vendo.run Happy to answer anything about the stack, agents, or YC. And I'll return the favor - drop your repo below and I'll star it too. 🙏

Hey everyone, I'm Yusuf, co-founder at Vendo (YC S26). Berkeley honors grad at 19, Stanford MS, and now building open-source software that lets companies agentify their products: embedded agents your customers use to automate work, build views, and connect their tools. We're at 412 stars and I'm trying to push past 500 so more builders find it. If you have a GitHub account, this takes 10 seconds: open https://github.com/runvendo/vendo and hit the Star button in the top right. That's it. Live product if you want to poke at it: vendo.run Happy to answer anything about the stack, agents, or YC. And I'll return the favor, drop your repo below and I'll star it too. 🙏

Most people use Claude Code the same way they use a chatbot — type a prompt, watch it work, respond to questions, babysit the output. That's fine for one-off fixes. But it doesn't scale. Here's the pattern I've been running instead: Claude Code as a background agent you dispatch tasks to, then walk away. The setup is simple: 1. Invoke Claude Code with --print and --permission-mode bypassPermissions 2. Pass a task description on stdin or as a prompt 3. It runs to completion and exits — no TTY required 4. Pipe the output wherever you need it (Telegram, log file, another agent) Example command: claude --print --permission-mode bypassPermissions "Fix the failing test in auth_service.py and commit the result" That's it. Claude reads the codebase, finds the test, fixes it, commits, and exits. You get a message when it's done. Where it gets powerful: • Schedule via cron — "every weekday at 9am, review open GitHub issues and draft fixes" • Chain agents — one agent researches, another implements, another reviews • Run multiple in parallel — different tasks on different branches simultaneously • Trigger on events — new PR opens, run a review agent automatically The key mindset shift: Claude Code is not a chat interface. It's a programmable worker. Once you stop treating it like a chatbot and start treating it like a subprocess, the whole thing opens up. What are you currently babysitting that you could delegate to a background agent?

Just published a free 5-lesson course for new members: 1. What is Claude Code? -- how it's different, who it's for 2. Install & First Session -- get up and running in 10 minutes 3. CLAUDE.md & Project Setup -- give your AI context so it stops guessing 4. Plugins, Skills & MCP Servers -- extend Claude Code with new capabilities 5. Customize Your Setup -- permissions, hooks, settings, context management Free for all members. Head to the Classroom to start. If you've already set up Claude Code, skip ahead to Lesson 3 -- CLAUDE.md is the single biggest improvement you can make.