Toolchain

This is Day 12 of the AI Path L1→L2 Upgrade Guide. Do Day 8, Day 10 and Day 11 first. Day 11 ended with a crucial question: How do we automate these steps? My approach relies on a simple realization: pairing stateless API calls with an AI agent shares the same core principles as breaking down workflows, designing systems, and building software. I’ve been doing that kind of work for years. The AI picture book project I’m building right now is a clean example. I’ll walk through how I designed its pipeline and tasks. ...

Spending the entire day inside OpenCode made my terminal my IDE. But when even typing became a problem, switching was the only option. This started with a very specific, very annoying problem: Chinese IME freezing. Inside Warp running OpenCode, typing Chinese was nearly unusable. Every three to five characters, the system would freeze for seconds. Input stopped responding. When it recovered, it would swallow some of the characters I’d typed. At first, I blamed OpenCode, thinking maybe it was consuming too many resources. But I checked other applications and typing was perfectly fine there. ...

This is Day 9 of Week 2 in the “AI Path L1→L2 Upgrade Guide.” You should have completed Day 7 Exercise: Add Error Handling to Your Script first. Day 7 added error handling to your script, so it’s resilient now. But there’s a bigger cost factor you might have missed: the API provider you picked could cost a lot more than you think. DeepSeek V4-Pro charges $0.435 per million input tokens. OpenAI GPT-5.5 charges $5.00. That’s roughly an 11.5x difference. Factor in caching and the gap widens further. ...

This is Day 8 of Week 2 in the “AI Path L1→L2 Upgrade Guide.” You should have completed Day 7 first. On Day 7, you added error handling to your script. It now runs reliably in real network conditions. But there’s a more fundamental limitation: you still have to write code. Writing code to call APIs is one kind of automation. There’s a lighter one: describe the task, and let AI write the code, run it, and fix the bugs itself. That’s autonomous execution AI. ...

This is the Day 7 exercise for Week 2 of the “AI Path: Level Up Guide” series. Complete Day 6: Batch Processing Practice first. In Day 6, you wrote a batch processing script that works. Pick a scenario, walk the folder, call the API, save the results. It all runs smoothly until you try it for real. But that script runs in an idealized environment. Real networks are not ideal. Have you hit any of these with your script? ...

This is the Day 6 exercise for Week 2 of the “AI Path: Level Up Guide” series. Complete Day 5: Teach Your Script to Read More File Formats first, then come back here to work through Day 6. In Day 5: Teach Your Script to Read More File Formats, you built the read_file() function and the skeleton of a batch script. Your script recognizes files in various formats now. But you haven’t run a full pipeline from start to finish yet. You still need to pick a scenario, call the API, and save the results. That loop is missing. ...

This is Day 5 of Week 2 in the “AI Path L1→L2 Upgrade Guide” exercises. Read Part 2 first, then come back here. The batch_summarize.py script from Part 2 handles .md and .txt files. But real files come in many more formats. PDF reports, Word contracts, CSV data tables, JSON config files. They’re sitting on your desktop right now, and the script can’t touch them. Today’s goal: write a read_file() function that picks the right reader based on file extension, then plug it into the Part 2 batch script. ...

This is Part 2 of the “AI Path L1→L2 Upgrade Guide” series. Complete Part 1 and the first three days of exercises (Day 1, Day 2, Day 3) before continuing. Part 1 taught you to make one API call. Today you’re going bigger: make your program ask AI 100 questions. Manually pasting text into a chat window 100 times is grunt work. Writing a 10-minute script to automate the task is worth it. You get the time back. ...

This is the Day 3 companion exercise. Complete Day 1 first. Part 1 covers the theory (“Understanding API Parameters”). Today you verify it with your own eyes. Part 1 explained parameters in theory. But theory without practice is just noise. Today you run three experiments and see for yourself how parameters affect output. Setup Make sure your Day 1 project still works: uv run python hello_api.py If the AI replies, your environment is ready. All experiments below build on this code. ...

This is the Day 2 companion exercise. Complete Day 1 first. Yesterday you ran your first API call through DeepSeek’s official API. Today you do one thing: switch to a different platform, change two parameters in the same code, and run it again. You’ll see that learning one platform’s API means you’ve learned them all, as long as they’re compatible with the OpenAI interface. What Is an Aggregator Platform An aggregator platform is a middle layer. You register one account, top up once, and get access to dozens of AI models (OpenAI, Anthropic, Google, etc.) without signing up at each official platform separately. ...