169Pi releases Alpie Seed, a 9B Apache 2.0 coding model that runs offline on a laptop. Plus vercel Schedules is in...

Make your agent ask setup questions one at a time. DeepSeek's dsh-superagent repo ships a SETUP.md written for the agent, not the person. You type one line and the file sets the rules: probe the machine first, ask one question per message with a recommended answer, run nothing until you confirm the full plan, and never ask for a secret in chat. Copy those rules into a SETUP.md for your own repo, and onboarding a teammate (or yourself on a new laptop) goes through your coding agent instead of a wiki page. The block below is DeepSeek's rules, shortened.

# SETUP.md (instructions for the agent)
- Before the first question, run <your probe commands> once. Skip any question the probe answers.
- Ask one question per message, with a recommended answer I can accept in one word.
- Don't execute while asking. Collect every answer, send the full plan in one message, and run it only after I confirm.
- A missing prerequisite goes into the plan, not into a question.
- Never ask for a secret in chat. Put steps that need my hands in one message with the exact commands.

Then ask your agent: Read SETUP.md in this repository and set up <project> with me.

Turn on caching for every turn of a Claude message thread. If you try Claude's new message threads, add one top-level field: cache_control set to ephemeral. A thread doesn't cache your prompt on its own. With that field, the API puts the cache breakpoint on the last cacheable block of each request, so every turn reads the earlier conversation from cache and writes the new turn to it. Send the exact same value on every request of the thread: it's a fixed field, and a different value returns thread_fingerprint_mismatch. A thread request can carry at most 4 breakpoints, and this one counts.

Headers on every request:
anthropic-beta: message-threads-2026-08-12

Turn 1 body (add to your usual request):
"cache_control": {"type": "ephemeral"},
"thread": {"type": "create"}

Every later turn (new messages only, no system or tools):
"cache_control": {"type": "ephemeral"},
"thread": {"type": "continue", "previous_message_id": "<id of the last response>"}

Write image edit prompts as the finished picture plus a keep list. When you ask an image model to edit a photo, describe how the finished image should look, then say what must stay the same. Pruna gives this pattern for P-H3-Image edits, and it pairs with their other prompt rules: say what the image is in the first sentence, put any text that must appear in quotes and keep it short, and leave out hype words like "masterpiece" or "8k", which they say push images toward a glossy, oversaturated look. If the first edit drifts, add the thing that changed to the keep list and run it again.