airs-workshop — module 1.3
~/airs environment setup --module 1.3 --tools claude-code

Environment Setup
& Claude Code

Get your tools ready. Meet your lab companion. Watch it build something live.

45
Minutes
10
Min Demo
15
Min Verify
20
Min Lab
The Bridge

Why You're Getting a Coding Tool

This week: deploy models, integrate APIs, build workflows, red team AI apps. Most of that is code.

What you'll do this week

Python scripts Docker containers CI/CD pipelines API integrations Security scanning Red team attacks

The analogy: You wouldn't hand-craft iptables rules when you have Panorama. Same principle. You're the security architect. Claude Code is the implementer.

Not all of you write code daily. That's fine. Claude Code writes the code — you drive the intent. It's not a nice-to-have. It is the lab environment.

The Tool

What Claude Code Actually Is

Agentic coding assistant in your terminal. Reads code, writes code, runs commands, iterates on failures.

CLI AGENT
Claude Code
→
INFERENCE
Vertex AI
MCP SERVERS
doc search
slack
vertex search
Endpoint: coe-airs-vertex — prompts stay within corporate boundary

Key differentiator: It's agentic. It doesn't suggest code — it executes, tests, sees failures, fixes, and retries. Autonomously.

Live Demo

Demo 1: Berg's Claude Code Setup

Switching to terminal. Watch — no action required yet.

💻
What You'll See
5 minutes — the art of the possible
  1. 1
    Agentic workflow — Claude Code writing, testing, and deploying code autonomously
  2. 2
    MCP integrations — searching the AIRS knowledge base, messaging Slack, voice responses
  3. 3
    Structured output — the PAI format you'll see in every lab this week

Takeaway: This is what you'll be able to do by the end of the week. Claude Code bridges the gap between your security expertise and the coding these labs require.

Live Demo

Demo 2: Let's Build Something Right Now

We need everyone in the lab GitHub org. Let's build the tool that does it.

# The prompt Berg will give Claude Code: Build a Slack workflow that accepts a GitHub username via slash command, validates the username exists on github.com, and adds them to our airs-labs GitHub organization. Use the gh CLI for GitHub operations.
🎯
Watch For
The process matters more than the result
  1. 1
    Reasoning — how Claude breaks down the problem
  2. 2
    Writing code — actual implementation, not suggestions
  3. 3
    Debugging — if it breaks (it might), watch the recovery
"This is real development. Things break. The debugging is often more impressive than the happy path."
Status Check

Where Are We? Hands Up

Quick pulse check. Be honest — that's what the next 20 minutes are for.

💻
Claude Code + Vertex
Installed, connected to coe-airs-vertex
Critical
☁
GCP Project
Project active with billing enabled
Critical
🔗
git + gh CLI
Both installed, configured, authenticated
Critical
🛡
CSP + AIRS Profile
Access to SCM with AIRS deployment profile
Day 2
🐍
Python 3.10+
With uv package manager
Today PM
🐳
Docker Desktop
Installed and running
Day 2

Missing 3+? Flag me or a TA right now. We'll get you sorted. Don't wait.

Lab Guide

Open the Lab Guide

Two sections. Work top to bottom. Don't spend more than 2-3 minutes stuck on anything.

Part 1 — Verify

What you should already have

Verify commands for every pre-work item. Don't assume — run the commands and confirm output.

Part 2 — New Setup

New for this week

git/gh CLI, GitHub org, vertex-search MCP, Python/Docker for model security lab.

Fix order if behind

  1. 1
    Claude Code working
    Blocks everything — every lab uses it
  2. 2
    GCP project accessible
    Blocks model security labs (Mon PM)
  3. 3
    git + gh CLI working
    Blocks lab repo access
  4. 4
    CSP / SCM access
    Blocks Days 2–5 — not a Day 1 stopper
airs-workshop — setup lab
~/airs lab start --module 1.3 --time 20min

Go Time. Set Up Your Environment.

Open the lab guide. Work through it. Raise your hand if stuck. Help your neighbor if done.

20
Minutes
7
Steps
Step 5
Claude Verifies
Step 6
Submit

When done: Claude Code is your lab partner for the rest of the week.

Advanced session (Module 3.6) on Day 3 — today is just getting you set up.