Pandai · 01 / 12

Using AI. Then bending it.

Two moves in AI engineering. Most people never get past the first one — and they're already 10× more capable than they were two years ago.

The arc

Three phases. Start with the first.

Phase 1

USING

Get good at the tools. Real use cases. Daily workflow.

Phase 2

SHIPPING

Build something real with them. Real artifact. Real user.

Phase 3

BENDING

Customize the tools to you. Your own MCPs, skills, loops.

What USING looks like

You can do amazing things without bending.

  • Meetings→notes, action items, follow-ups
  • WhatsApp transcript→summary in 10 seconds
  • KTP photo→structured data, copied to clipboard
  • Itinerary for Bali→30 seconds, not 3 hours
  • Bank statement→ledger CSV, ready for accountant

You’ll need a coding agent

Today’s options.

The criterion is whether the agent uses your Chrome session, not its own. Your real browser is signed into Vercel, Twilio, your bank, your email. That auth is the agent’s superpower.

defaultClaude Codechrome-aware, reliable
also-goodPi"this one is yours"
maybeCodexuntested
avoidCursorspawns its own Chrome
avoidClinespawns its own Chrome

Your turn

Pick one real annoyance. Use AI to make it go away.

Something you’ve manually done more than three times this month. Spend an hour. Use the coding agent. Ship the artifact.

(When apps/academy ships, this section gets a SHIP-submission form: GitHub URL, Loom URL, short writeup. Instructor reviews and leaves feedback.)

This is a preview of the academy module experience. The free curriculum arc lives at /open .