Day 6 of #100DaysOfAmp
Cloud orbs hit two walls on the web: blocked datacenter IPs and login screens.
With Amp Net + Browser Sync, an orb borrows your Mac's network and Chrome cookies in 3 steps:
1. Enable Settings → Experimental Features → Amp Net
2. Start your local runner:
$ amp --no-tui --runner-id my-mac --share-network --share-browser
3. Inside the orb, run:
$ amp net route my-mac
$ amp orb desktop ensure
$ amp sync browser
Your Mac becomes the exit node and your cookies drop straight into the orb's Chrome—no re-login needed.
3 sharp edges from testing:
• Google Chrome default profile only: missing Default/Cookies returns HTTP 503
• --domains only works when publishing on your Mac, not importing in the orb
• Still a Linux fingerprint: your IP and cookies, but a Linux browser—skip for strict anti-bot accounts
Day 5 of #100DaysOfAmp
When you write, what you lack is rarely a pen. It's three things: someone to ask, a book to check, and someone to review.
ASK — the question. You're stuck on whether to keep a sentence. It doesn't decide for you. It holds up two cards and waits. If you don't pick, it doesn't move.
LIBRARIAN — the lookup. You ask whether an API changed last month. It walks the shelves on GitHub: public repos, plus the private ones you've authorized, default branch only. It comes back with a long answer. It does not read your local files.
ORACLE — the review. You finish a draft and aren't sure. It reads the whole thing and circles "this has no evidence" and "these two options are the same option." It reads and never writes. Whether to change anything is still your call.
None of them write for you. They just make sure that while you write, someone is there to ask, something is there to check, and someone is there to review.
Grok Promo Code: 1 Month Free Premium (Referral)
sharecodekit.com/grok
Day 4 of #100DaysOfAmp
The hard part of a new tool is not the tool. It is the environment.
A non-technical teammate can't run Codex on their laptop. A skill needs a CLI that isn't installed. Three machines, three different errors.
Put the install in .agents/setup. One orb runs it once, Amp saves the result as a project snapshot, and every later orb starts from that snapshot instead of a blank machine. Teammates skip the install entirely.
1. Set up once, reused across threads and project members.
2. Starts in seconds: the snapshot already has the tools.
Billed by the minute. a1.small is $0.17/hour, and a paused orb costs nothing.
3. Limits worth knowing: a snapshot is reused for up to 72 hours, setup is cut off after 20 minutes, and editing .agents/setup does not invalidate the snapshot you already have.
Setup stops being a rite of passage.
Day 3 of #100DaysOfAmp: a little-known fact.
Amp Free is paused for most people. Mine still works: $5 a day, reset every morning at 8.
Amp once promised some of us this daily grant. When it ended free credits for everyone else, it kept that promise.
My card now says "Expiring Soon." Fair enough. A promise kept to the end is still a promise kept. It's a big reason 2,000+ of my threads live in Amp.
No grant? The Hobby tier is still free with your own ChatGPT or Claude sub.
Day 2 of #100DaysOfAmp
I run a handful of Amp threads at once. The annoying part was clicking into each one to see if it was waiting on me.
Turn on Settings → Experimental Features → "Jev Labels the Sidebar". The sidebar gets a status bar: Needs You, Review, Blocked, Waiting, Done. Jev reads the latest messages and sorts each thread. Click a status to filter.
Now I glance at the bar and go straight to the thread that needs me.
