#beginner
Every post tagged "beginner".
42 posts · showing 1–10
-
Your Inbox Agent Wakes Every 15 Minutes to Find Nothing. Cron or Event Trigger? Decide by What a Wasted Run Costs.
The trigger is the least-discussed design choice in a personal agent, and it quietly decides your bill, your duplicate rate and how stale its answers are. A simple test for choosing between a schedule and an event, and why the best setup usually uses both.
-
One Big update_task Tool or Three Small Ones? Your To-Do Agent Only Sees the Names and Descriptions
A to-do agent archived a task you meant to finish, and the tool was working fine. The model picks tools from a short menu of names and descriptions, so how you split that menu decides how often it picks wrong.
-
Your Scheduling Agent Moved One Meeting and Said "Done." Teach the Loop What Finished Looks Like.
An agent loop ends when the model stops asking for tools, not when your task is finished. Here is why that gap produces confident half-done work, and a small done-check that closes it.
-
The Agent Said It Booked the Meeting. Learn to Read One Turn: Text, Tool Call, Tool Result, and Which One Counts
An agent's reply can describe an action it never took. Once you can tell the three kinds of message in a transcript apart, you will know in ten seconds whether the calendar invite exists.
-
An Agent That Cannot Fail Will Retry Forever. Budget Tokens and Wall-Clock, Not Retry Counts.
Your max_retries=3 never fires, because every search call succeeds. The agent just keeps finding new ways to look for an answer that doesn't exist. Here is the budget that actually stops it, and the exit that lets it stop politely.
-
Your Agent Called the Same Tool Three Times in a Row. Here's What the Loop Is Telling You.
A repeating agent isn't being stubborn — it's being consistent. Identical tool calls mean the context barely changed between turns, and there are only four reasons that happens.
-
When the Context Window Fills, Cut in This Order — and Leave a Stub Behind
Most agents evict context by dropping the oldest tokens, which reliably deletes the nine words that mattered while keeping a 4,000-token HTML dump nobody needs. Here is the order to cut in, and why every eviction should leave a stub behind.
-
Agent or Just a Script? Count the Branches That Depend on Reading Something
There is a ten-minute test that settles whether your automation needs an agent loop or just a script with a couple of model calls in the middle — and the two ways of guessing wrong are not equally recoverable.
-
Your Agent Has One manage_calendar Tool. That's Why It Deleted the Wrong Meeting.
A single do-everything tool looks tidy in the schema and hides four separate problems: guessed actions, unvalidated payloads, permissions that can't tell reading from deleting, and traces that flatten three risk levels into one name. Here's where to cut instead — and where splitting makes things worse.
-
Do You Need an Agent Framework? Write the 40-Line Loop First
The agent loop is shorter than the quickstart for the framework that hides it. Write it once — then you can tell which framework features you actually need and which ones you'd be adopting on faith.