nader dabit

My favorite thing about my @moltbot is how simple it is to create cron jobs that deliver tons of personally curated + high value information to me every morning to start my day. Here are the jobs I have set up so far. 1. GitHub trending digest Top 10 trending repos with stars, language, and quick takes on why each is interesting, grouped by category. 2. Daily motivation 10 timeless motivational tweets about building, shipping, and momentum - my morning fuel 3. Top Hacker News stories Top 10 upvoted Hacker News posts from the past 24 hours summarized with links 4. Product Hunt Daily Picks Best 5-7 launches from PH, focused on dev tools and AI products, includes upvote counts and whether it's worth my attention. 5. YC Startup Spotlight Deep dive on one YC company - problem, solution, founders, funding, competitors, and analysis. mini investor memo style 6. AI twitter digest Top 20 viral AI tweets from the past 24 hours 7. I also have a daily AI trend app builder It searches X for viral AI trends, picks one, and actually builds a working app inspired by it and pushes to my GitHub and sends me the link I feel like this will replace almost all newsletters I'm subscribed to as the content is much more curated to exactly what I want. And this has been done with very minimal work, so I feel like I'm just scratching the surface

I think we're hitting a point where mobile coding actually makes sense for production-grade systems. This developer runs 6 Claude Code agents in parallel from his phone. No laptop, just a $7/day VM and push notifications when Claude needs input Instead of long periods of intense focus, software development can now just fit into the gaps of your day.

A new (beta) feature of Claude that I've been learning about today is Programmatic tool calling. It programmatically writes code that calls and runs your tools directly in a sandbox before returning results to the model. This reduces latency + token consumption because you can essentially filter or process data before it reaches the model's context window. https://platform.claude.com/docs/en/agen……

If you've used Claude Code, you've seen what an AI agent can actually do: read files, run commands, edit code, figure out the steps to accomplish a task. And you know it doesn't just help you write code, it takes ownership of problems and works through them the way a thoughtful engineer would. The Claude Agent SDK is the same engine, yours to point at whatever problem you want, so you can easily build agents of your own. It's the infrastructure behind Claude Code, exposed as a library. You get the agent loop, the built-in tools, the context management, basically everything you'd otherwise have to build yourself. This guide walks through building a code review agent from scratch. By the end, you'll have something that can analyze a codebase, find bugs and security issues, and return structured feedback. More importantly, you'll understand how the SDK works so you can build whatever you actually need. ## What we're building Our code review agent will: - Analyze a codebase for bugs and security issues - Read files and search through code autonomously - Provide structured, actionable feedback - Track its progress as it works ## The stack • Runtime - Claude Code CLI • SDK - @anthropic-ai/claude-agent-sdk • Language - TypeScript • Model - Claude Opus 4.5 ## What the SDK gives you If you've built agents with the raw API, you know the pattern: call the model, check if it wants to use a tool, execute the tool, feed the result back, repeat until done. This can get tedious when building anything non-trivial. The SDK handles that loop: You also get working tools out of the box: • Read - read any file in the working directory • Write - create new files • Edit - make precise edits to existing files • Bash - run terminal commands • Glob - find files by pattern • Grep - search file contents with regex • WebSearch - search the web • WebFetch - fetch and parse web pages You don't have to implement any of this yourself. ## Prerequisites - Node.js 18+ installed - An Anthropic API key (get one here) ## Getting started Step 1: Install Claude Code CLI The Agent SDK uses Claude Code as its runtime: After installing, run claude in your terminal and follow the prompts to authenticate. Step 2: Create your project Step 3: Set your API key ## Your first agent Create agent.ts: Run it: Claude will use the Glob tool to list files and tell you what it found. ## Understanding the message stream The query() function returns an async generator that streams messages as Claude works. Here are the key message types: ## Building a code review agent Now let's build something useful. Create review-agent.ts: Testing It Out Create a file with some intentional issues. Create example.ts: Run the review: Claude will identify the bugs, security issues, and suggest fixes. ## Adding Structured Output For programmatic use, you'll want structured data. The SDK supports JSON Schema output: ## Handling permissions By default, the SDK asks for approval before executing tools. You can customize this: Permission modes Custom permission handler For fine-grained control, use canUseTool: ## Creating subagents For complex tasks, you can create specialized subagents: ## Session management For multi-turn conversations, capture and resume sessions: ## Using hooks Hooks let you intercept and customize agent behavior: ## Adding custom tools with MCP Extend Claude with custom tools using Model Context Protocol: ## Cost tracking Track API costs for billing: ## Production code review agent Here's a production-ready agent that ties everything together: Run it: ## What's next The code review agent covers the essentials: query(), allowedTools, structured output, subagents, and permissions. If you want to go deeper: More capabilities • File checkpointing - track and revert file changes • Skills - package reusable capabilities Production deployment • Hosting - deploy in containers and CI/CD • Secure deployment - sandboxing and credential management Full reference • TypeScript SDK reference • Python SDK reference > This guide covers V1 of the SDK. V2 is currently in development. I will update this guide with V2 once it's released and stable. If you're interested in building verifiable agents, check out the work we're doing at @eigencloud here.