> Max Bell School of Public Policy
You can just do things
CLI agents for policy work
By the end of this session
- Open a terminal and use it without fear
- Understand what a CLI agent is and how it differs from a chatbot
- Use an agent to research, structure, draft, and iterate on a policy memo
- Evaluate agent output critically (know where it helps and where it misleads)
- Deliver an oral brief on a memo you built with an agent
- Know where to go to keep learning and tinkering
Agenda
- Foundations — terminals, agents, the mental model (10 min)
- The landscape — tools, permissions, setup (10 min)
- Live demo — building a policy memo from scratch (15 min)
- Your turn — hands-on memo exercise (40 min)
- Oral briefings — stand up and defend it (20 min)
- Where to go from here — tinkering, tools, next steps (10 min)
Cheaper to build it than to have the meeting
“It is literally cheaper to build the thing and see if it works than to have a 30 minute planning meeting about whether you should build it.”
— Todd Saunders (some random dude on the internet)
- The cost of trying things has dropped to near zero
- Don’t debate whether an analysis is feasible — just try it
- Don’t wonder if the data supports your argument — just check
- Every decision can be informed by a real investigation, not a hypothetical
What is a terminal?
- The text interface underneath every computer
- Everything you do with a mouse can be done with text
- GUIs are slow and bounded. CLIs are powerful.
- You type what you want in plain language. The agent does the work.
$ gemini > Create a folder called "memo" and draft a 1-page policy brief on algorithmic regulation in Canada ✓ Created memo/ ✓ Wrote memo/brief.md (1,247 words) — Problem statement, 3 policy options, recommendation
Chat vs. agent
Chatbot
- Answers questions
- Lives in a browser tab
- You copy-paste output
- No memory between sessions
- Can't touch your files
Chat vs. agent
Chatbot
- Answers questions
- Lives in a browser tab
- You copy-paste output
- No memory between sessions
- Can't touch your files
Agent
- Does work — reads, writes, runs code
- Lives in your terminal
- Edits files directly
- Sees your project context
- Asks permission before acting
You are the manager. The agent is the intern.
- You wouldn’t hand an intern a task and accept the first thing back without reading
- You give direction, context, and judgment. The agent gives speed and breadth.
- The quality of the output depends on the quality of your direction.
- Good: “The problem statement doesn’t explain why this is urgent for Canada specifically”
- Bad: “Make this better”
The agent writes fast. Your name goes on it. You are responsible for every claim, every citation, every recommendation.
Numerous CLI agent options

Claude Code
Anthropic · $20/mo (Pro)
curl -fsSL https://claude.ai/install.sh | bash

Codex
OpenAI · $20/mo (Pro)
npm i -g @openai/codex

Gemini CLI
Google · Free tier available
npm install -g @google/gemini-cli
OpenCode
Open-source · Free (BYOK)
curl -fsSL https://opencode.ai/install | bash
Learn the pattern, not the product. The skill transfers across all of them.
The permission model
- The agent proposes actions. You approve or deny each one.
- Write a file? Ask first. Run code? Ask first. Search the web? Ask first.
- You can grant broader permissions as trust builds
Gemini wants to run: python analyze.py --input survey_data.csv Allow? [y] Yes [n] No [a] Always allow > y
You are responsible for what runs on your machine and what gets produced under your name.
The task
Something I know nothing about. Let’s pick a topic live.
What we’ll do live:
- Research: outline the landscape, search for recent developments
- Structure: standard policy memo — context, problem, options, recommendation
- Draft: generate a first version
- Iterate: sharpen the argument, add evidence, challenge the recommendation
- Verify: check citations, identify weak spots
What to watch for
Where it shines
- Structure and organization
- Breadth of coverage
- Speed of iteration
- Responding to specific feedback
Where it stumbles
- Hallucinated citations (or bad ones)
- Recency of information
- Normative judgment calls
- Nuance in contested debates
- Agreeability bias
The agent is fast and confident. That combination is dangerous without YOU!
The exercise (40 min)
Steps
- Research — key arguments, frameworks, stakeholders (10 min)
- Structure — problem, context, options, recommendation (5 min)
- Draft — generate a 1-page memo (5 min)
- Iterate — sharpen, challenge, add evidence (10 min)
- Prepare to brief — if you can’t explain it, go back (10 min)
Topics
- Algorithmic recommendation regulation
- AI in public services
- Short-term rental policy
- News media sustainability
- Foreign information operations
- AI in immigration decisions
Or bring your own topic.
Tips while you work
- Be specific: “the problem statement doesn’t explain why this is urgent for Canada specifically”
- If the agent gives you a citation, ask it to verify or check it yourself
- Try: “What’s the strongest counterargument to my recommendation?”
- If you’re stuck, ask the agent to critique your draft
- Remember: you can just do things. Want a comparison table? Ask. Want a chart? Ask.
Stand up and defend it
Format
- 2 minutes: state the problem, your recommended option, and why
- 1–2 questions from the class
If you can’t explain the argument clearly, justify the recommendation, and answer a question — the memo isn’t yours yet.
The point
- The agent produces polished text quickly
- You have to stand up and defend it
- The oral brief is a forcing function
- If you have to explain it out loud, you have to understand it
Sandbox: keep it in one folder
Agents can read and write files. Limit the blast radius by starting them inside a dedicated project folder.
# 1. Create a project folder mkdir ~/my-project && cd ~/my-project # 2. Start the agent FROM that folder gemini # 3. Tell it: "Only work within this folder" # The agent will ask before touching anything outside
- The agent inherits the folder you launch it in as its working directory
- It asks permission before creating or editing files — read before you approve
- Keep sensitive files (passwords, credentials, personal data) elsewhere
- When in doubt, start a fresh folder for each new experiment
Finding new capabilities
- MCP (Model Context Protocol) — plug in new tools: databases, APIs, Slack, Google Docs
- Custom instructions — teach the agent your preferences, your style, your project context
- Skills and workflows — build reusable prompts for tasks you do repeatedly
- Community — GitHub, Twitter/X, Reddit — people share workflows constantly
- New features ship every week across all providers
The tinkering mindset
- The best way to learn is to try things and see what happens
- There is no “correct” way to prompt — experiment, iterate, be curious
- When something doesn’t work, ask the agent why and try a different approach
- Build up your own toolkit over time
- The people who get good at it are the ones who play with it
The gap between people who tinker with these tools and people who don’t is going to widen fast.
What to remember
The oral brief keeps you honest. If you can’t explain it, you don’t understand it.
Your name, your responsibility. The agent writes fast, but every claim is yours to defend.