AI Resources

• It reads on its own. A chat tool reads what you paste. An agent reads what it finds — files in a folder you point it at, messages in a connected inbox, web pages it decides to visit. You set the scope; it picks what to look at within that scope.
• It acts; it doesn’t just describe. A chat tool will tell you the command to delete duplicate files. An agent will run the command. A chat tool will draft an email. An agent will send it.
• It plans across many steps. Agents work in a loop: form a plan, take an action, observe the result, revise the plan, take the next action. A single instruction from you might trigger dozens of intermediate steps.
• It uses “tools.” In AI parlance, a tool is anything the agent can call: read a file, run a terminal command, fetch a webpage, send an email, query a calendar. The tools available define what the agent can do. Adding a connector — like Gmail or Google Drive — expands the agent’s reach.
• It works between your prompts. The agent may be working for a minute or for ten between your messages. It doesn’t pause to ask permission for every step unless you’ve configured it to.

• Speed and scope. Agents can do in minutes what would take hours of clicking and typing. The flip side is that they can also do damage in minutes.
• Reviewability. Chat outputs are text you can read. Agentic outputs are actions: files changed, messages sent, calendar invites accepted. Reviewing what an agent did is more involved than reviewing what a chatbot wrote.
• Trust setup. With chat, you decide each turn what to share. With an agent, the agent decides what to read within whatever scope you’ve granted. That makes the initial setup — folder, permissions, connectors — far more consequential than what you paste into any single chat.
• Reversibility of errors. Chat errors are wrong answers you can ignore. Agent errors are wrong actions — a deleted file, a misdirected email, an inappropriately scheduled task. Some are easy to undo; some are not.

Chat AI suits drafts, summaries, explanations, brainstorming, and questions where the input fits in a message and the output is text you’ll review.

Agentic AI suits tasks that span many files, require chained steps, or involve making changes rather than describing them — particularly repetitive or well-defined work.

A note on terminology: “Agent,” “assistant,” “copilot,” and “AI tool” are used loosely and inconsistently across products. The distinction that matters isn’t the label — it’s whether the tool can take action on your behalf without each step being explicitly approved. If it can, treat it as agentic, and apply the cautions in the security guide.

Claude Code is Anthropic's AI coding and productivity tool — it works in your terminal, in VS Code, as a desktop app, or in your browser. Despite the name, it's not just for coding. I use it for writing, research, document production, and administrative tasks. It's the tool behind the Claude Code Skills listed on this page and on the pedagogy portal.

You need a paid Claude subscription (Pro, Max, Team, or Enterprise) to use it. The free tier won't cut it — you need the pro models and the privacy controls that come with a paid plan.

Getting Started

• Overview & installation — install the CLI, VS Code extension, or desktop app
• Quickstart — walk through your first task
• Law faculty skills — my open-source skills for faculty tasks (install instructions in the README)

If you want help getting set up, email me — I'm happy to walk you through it.

The agentic tools above are prebuilt. If you'd rather build your own — automate a repeat task, process a batch of documents, or wire a model into a script — you can call the models directly through an API. You don't need to be a software engineer: if you can write a basic script (or have an AI write one for you), you can use one.

Why Use an API?

The conversational tools are great for one-off tasks. But if you find yourself doing the same thing over and over — processing a batch of documents, grading with a rubric, extracting data from a set of files — an API lets you automate it. You write a script once, and it runs the same prompt across hundreds of inputs without you copy-pasting anything.

APIs also give you more control: you can choose the model, adjust parameters like temperature (how creative vs. deterministic the output is), and build multi-step workflows where the output of one call feeds into the next.

The Penn LLM Gateway

Penn runs a secure LLM Gateway that provides programmatic API access to a range of models from inside Penn's environment — built for research and tool-building. Penn Carey Law is part of the pilot program. It's the Penn-sanctioned path to API access, as opposed to a personal vendor account, which makes it the right starting point for work that touches Penn data or is funded by Penn. Email me to get connected.

Anthropic (Claude) API

If you'd rather go straight to a vendor, Anthropic's API gives you direct access to the Claude models — the same ones powering Claude Code and the Claude chat interface, but programmatically. Strong at writing, analysis, long documents, and coding tasks.

• Documentation
• Getting started
• Pricing — pay per use; starts at a few dollars for significant usage

OpenAI API

OpenAI's API gives you access to the GPT-5 family of models — the same models behind ChatGPT, but with full programmatic control. Broad capabilities across writing, reasoning, and multimodal tasks.

• Documentation
• Quickstart
• Pricing

Other Models

The AI model landscape is broader than just Anthropic and OpenAI. Google's Gemini models are available through their API with similar capabilities. There's also a growing ecosystem of open-source models — Meta's Llama, Mistral, and others — that you can run locally or through hosting providers, sometimes for free. I'm happy to discuss options if you're exploring this space.

If you're interested in working with APIs and want help getting started, email me. I can point you to examples and walk through the basics.

Working directory hygiene

Create a dedicated working folder for AI sessions — not your home directory, not your Desktop. Use a separate folder for each project and limit the agent’s access to that folder. Only put files in there that you’re comfortable with the agent reading — whatever’s in the folder, the agent can and likely will read.

Conservative connectors

Each connector (Gmail, Drive, Calendar, MCP servers) expands what the agent can see and act on. Enable only what you’re actively using. For now, faculty cannot connect external agentic AI tools to the Law School’s O365 — email, calendar, OneDrive, Teams. Faculty experimenting with other connectors should use personal, non-Penn accounts. Email and calendar connectors of any kind deserve special care — they can send messages and accept invites on your behalf.

Guard against prompt injection

Malicious instructions can be hidden in documents, emails, or web pages an agent reads — and the agent will treat them as commands from you. A PDF that instructs the agent to write a favorable evaluation; an email that instructs a Gmail-connected agent to forward messages externally. Be skeptical when an agent’s behavior changes after it reads external content, and keep sensitive actions (send, delete, network calls) gated behind explicit approval.

Most people try an AI tool once, get a mediocre answer, and conclude it's not that useful. The difference between a mediocre answer and a genuinely helpful one usually comes down to how you ask. Here's what I've learned works.

Be Specific About What You Want

Don't just say "write me a memo." Say "write a two-page memo to the faculty curriculum committee recommending we add a course on AI regulation, in a professional but collegial tone." The more you specify — format, length, audience, tone — the better the output. Vague prompts get vague results.

Give It Context

AI tools work dramatically better when you give them something to work with. Paste in the document you want summarized. Copy in the email thread you need to respond to. Describe the situation in enough detail that a smart colleague could help you. Context is the single biggest lever you have.

Iterate — Treat It as a Conversation

The first response is almost never the final product. Push back. Say "make this more concise" or "you missed the point about X" or "rewrite the second paragraph in a more formal tone." These tools respond well to iteration, and the back-and-forth is where the real value emerges.

Ask It to Critique Its Own Work

One of the most underused techniques: after the AI gives you a draft, ask it to identify weaknesses in what it just wrote. "What are the strongest objections to this argument?" or "What did you leave out?" This often surfaces issues you'd catch on your own — but faster.

For a more detailed guide to prompting, the AI Teaching Lab has a comprehensive resource:

From the Lab: the AI Teaching Lab builds tools for much of this — exam grading, question generation, custom casebooks, a course-bound virtual TA, and more. See what the Lab has built →

Faculty often ask which tool to pick. As of July 2026, here’s my honest read.

I keep pro-level paid accounts on all three major AI vendors — Anthropic (Claude), OpenAI (ChatGPT), and Google (Gemini) — so I can compare them on real work and notice when one pulls ahead. About 90% of my actual use runs through my Claude Max subscription, accessed via Claude Code in the macOS terminal. The CLI interface isn’t a requirement — it’s just where I’m fastest — but the Max tier matters because Claude Code burns through usage limits faster than Pro can sustain for heavy use.

My current recommendation: for most faculty work — drafting, research synthesis, document workflows, data analysis — Anthropic’s Claude models are the best choice today. That’s a current-state read, not a permanent claim; the landscape moves fast and the right answer changes. If you want a single starting point, Claude Pro + Claude Code (in whatever interface you find comfortable — terminal, desktop app, VS Code) is what I’d pick first.

New to Claude Code? Start with the basics on the Getting Started tab. If you've already set it up and want to do more, here are some features worth knowing about.

CLAUDE.md — Persistent Instructions

Drop a file called CLAUDE.md in any project folder and Claude Code reads it at the start of every session. Use it for coding standards, project context, preferred conventions — anything you'd otherwise repeat every time. I use mine to set voice and formatting preferences so I don't have to re-explain them. Documentation →

Custom Skills

Skills are reusable prompts you can install and invoke by name — like /commit or /review-pr. The law faculty skills I've built are examples of this. Built on the open Agent Skills standard, they work across tools — Claude Code, ChatGPT, Gemini CLI, and a growing list of compatible agents. You can also create your own for any workflow you repeat. Documentation →

MCP — Connecting to External Tools

The Model Context Protocol lets Claude Code connect to external services — Google Drive, Gmail, calendars, databases, Slack, and more. Useful for personal workflows that don’t involve Penn data. For now, faculty cannot connect external agentic AI tools to the Law School’s O365 (email, calendar, OneDrive, Teams) — so keep MCP connectors pointed at personal, non-Penn accounts only. Documentation →

Multiple Environments

Claude Code works in the terminal, VS Code, the desktop app, and the web. Your account, projects, and history follow you across all of them. Start a task on your laptop, pick it up from your phone. (Local settings and MCP servers are a different story across two separate machines — see Using Claude Across Two Computers below.)

Full documentation: code.claude.com/docs

A common question: if I set something up on my office machine, will it be there on my home machine? The answer depends on which Claude product you mean. Claude Projects and Cowork’s task history are tied to your account and follow you everywhere. Claude Code is a local developer tool and needs one of two specific features to get the same effect. And Cowork’s own internal “Projects” are the one real exception — local-only, with no sync at all.

Claude Projects (claude.ai)

Projects are tied to your Claude account, not to a device. Once you’re logged in, the same projects, knowledge files, custom instructions, and chat history are available on any computer, the desktop app, or your phone — no manual syncing. Two caveats: full project functionality requires a paid plan (Pro, Max, Team, or Enterprise), and if your account is managed by an organization, that org’s settings can affect access independent of Claude itself.

Claude Cowork

Cowork’s conversation and task history work the same way: sessions run on Anthropic’s servers and follow your account, so you can start a task on one computer, check progress from your phone, and pick up the finished output on another computer — all in one continuous thread.

The exception is local file access. Cowork reaches your actual computer only through the Claude Desktop app running on that specific machine. Folder connections are granted per device — connecting a folder on your home computer does not carry that permission to your office computer, even if both machines see the identical folder through Dropbox or another sync tool. You have to open the folder connector in the Desktop app and grant access on each machine separately.

Cowork also has its own “Projects” feature — workspaces that group related tasks with their own files, context, and memory — and this is not the same as the claude.ai Projects above. Cowork projects are desktop-only and stored locally, with no cloud sync. A Cowork project created on your home computer will not appear on your office computer, and there’s currently no setting that changes this. The workaround is to recreate the project on the second machine (pointed at the same connected folder) or skip the project grouping and run tasks directly. Documentation →

Claude Code

Claude Code is the most device-local of the three. Installed separately on two machines, each install is independent: user-level configuration and MCP servers you added locally on one machine don’t appear on the other. To share configuration across machines, commit it into the project’s git repository (a CLAUDE.md and an .mcp.json in the repo travel with the code); user-level settings in ~/.claude stay put unless you sync that folder yourself.

Two features give you real continuity across machines:

• Claude Code on the web runs sessions on Anthropic’s cloud infrastructure instead of on either computer. Start one from a terminal with claude --cloud, or directly at claude.ai/code; check it from a browser or the mobile app; and later pull it into a terminal on a different machine with claude --teleport. Teleport needs the repository on GitHub with your branch pushed, and a checkout of that repo on the machine you’re pulling into. Documentation →
• Remote Control lets you steer a session actively running on one machine from another device — your phone, a browser, or another computer. The original machine has to stay on and keep running: this is for steering from elsewhere, not full portability. Documentation →

Troubleshooting

A Dropbox-synced folder isn’t reachable in Cowork on my second computer. Expected behavior, not a bug. Folder connections are granted per computer, so even though the folder is physically synced to both machines, the Desktop app has to be opened and the folder explicitly reconnected on each machine. Open the folder connector in the Desktop app on the second computer and add the same folder there.

My Cowork projects don’t show up on my other computer at all. A real product limitation, not a settings problem. Cowork’s internal Projects feature is local-only with no cloud sync (unlike claude.ai Projects, which do sync). Recreate the project on the second machine, or work without the project grouping and rely on directly connected folders instead.

The Penn Data Risk Classification

Penn classifies data into three tiers — Low Risk (publicly available; no harm if disclosed), Moderate Risk (not generally public; mildly adverse if disclosed), and High Risk (regulated or sensitive; significantly adverse if disclosed). Most legal teaching, scholarship, and administration touches Low and Moderate Risk data. Personnel matters, student PII, confidential committee deliberations, and similar sit at Moderate or High. The full framework is at isc.upenn.edu/security/penn-data-risk-classification.

AI Tools Reviewed by Penn Law ITS (as of July 2026)

Per Penn Law ITS's AI Tools & Guidance page, the following tools have been reviewed and endorsed for use with Penn data at PCL:

• PennChat — Penn's secure, University-hosted AI portal (Anthropic's Claude and OpenAI's ChatGPT, chat only), free during the pilot. Approved for Low, Moderate, and most High Risk Data (excluding SSNs and credit-card data; avoid identifiable PHI) — the broadest data approval at PCL, alongside Microsoft Copilot Chat. Requires PennNet / AirPennNet or the GlobalProtect VPN. See the PennChat FAQ.
• Microsoft Copilot Chat — free for all PCL faculty, staff, and students via Penn's Microsoft enterprise agreement. Approved for Low, Moderate, and most High Risk Data (excluding SSNs and credit card data) — matching PennChat as the broadest data approval among general-purpose AI tools at PCL. Web-based AI search, content generation, and summarization. See the PCL ITS Copilot Chat Guide.
• Harvey AI — legal-AI platform via Penn Law's enterprise agreement. Approved for Low and Moderate Risk Data only; do not input high-sensitivity data (clinical, HIPAA/PHI, financial account information, SSNs, or credit cards). Available to full-time faculty, staff, and 2L/3L/LLM students (not 1Ls). LawKey login at app.harvey.ai.
• Legora — new legal-AI platform arriving ~August 2026 (agreement being finalized). Anticipated approval for Low and Moderate Risk Data, to be confirmed at rollout.
• ChatGPT EDU — approved for Low and Moderate Risk Data only. No HIPAA/PHI, financial account information, SSNs, or credit cards. Remains available to faculty and staff (students are moving to Claude for 2026–27); request access via Penn Law ITS. See the ChatGPT EDU FAQ.
• Claude — arriving school-wide under a University agreement expected ~August 2026 (faculty via research accounts; 1Ls via the 1L Legal Practice Skills curriculum). Anticipated approval for Low and Moderate Risk Data, to be confirmed at rollout.
• Zoom AI Companion — in-meeting AI for Zoom: live questions, meeting summaries, smart recordings. Available to full-time faculty, staff, and students with a Penn Zoom account. See the PCL ITS Zoom AI Companion Guide.

Penn ISC's central list reviews additional tools beyond those above — Microsoft 365 Copilot (the premium tier embedded in Office apps; requires a paid per-user license), Gemini for Google Workspace, Google NotebookLM, Grammarly, and others — with their own per-tier mappings. Availability for PCL community members varies; the full Penn-wide list is at Penn Generative AI Tools & Resources. Westlaw AI and Lexis+ AI are covered separately under Penn Law's existing legal research subscriptions.

For AI tools beyond those Penn Law ITS or Penn ISC has reviewed, the framework is the same one Penn applies internally: identify the risk tier of any Penn data involved, check the vendor's data-handling terms, and reach out to Penn Law ITS or me with use-case-specific questions.

Quick Guidance for Law School Work

For teaching prep, scholarship drafting, summarizing public legal materials, and most administrative tasks, the PCL ITS-reviewed tools above work well. For sensitive Penn data — student PII, personnel matters, confidential committee deliberations — PennChat and Microsoft Copilot Chat have the broadest approval among the PCL-reviewed tools (Low, Moderate, and most High Risk); Harvey, ChatGPT EDU, and Zoom AI Companion are reviewed for Low and Moderate Risk only. For SSNs, credit card data, or HIPAA-protected information: don't put it into any AI tool, period.

Personal-Account Use of Other Tools

If you're using Claude, ChatGPT (consumer version, not EDU), or any other AI tool on a personal account rather than through Penn's institutional access, the Penn approvals above don't apply — you're operating under that vendor's terms. Always use the paid tier, the strongest model available, with training opt-outs enabled. Free tiers may use your inputs as training data and lack the privacy controls. Personal-account tools should never see Penn's Moderate or High Risk Data.

Agentic AI tools — Claude Code, OpenAI Codex, Gemini CLI, Claude Cowork, and the agentic features inside Claude and ChatGPT — introduce risks the data-classification framework above doesn’t fully cover. They read files on their own, take action on your behalf, and can be misdirected by content they read from external sources. The data-classification rules still apply, but the operational practices that protect Penn data look different.

Full treatment is in the dedicated Agentic AI tab and in the standalone security guide:

AI Hallucinates — Verify Everything That Matters

I said this in the Getting Started tab, and I'll say it again here because it's the single most important thing to understand about these tools: LLMs generate plausible text, not verified truth. They will fabricate case citations, invent statistics, and present made-up facts with complete confidence.

This isn't a minor issue. A lawyer was sanctioned for filing a brief with AI-fabricated case citations. Law review articles have been submitted with invented sources. It happens because the output looks right — and when you're moving fast, it's easy to trust it. Don't. Anything you plan to rely on, share externally, or put your name on should be independently verified.

Attribution

When and how to disclose AI use is still evolving, but the direction is clear: transparency is the right default. If AI contributed meaningfully to a piece of work, say so. For faculty publications, grant applications, and student-facing materials, err on the side of disclosure.

Professor Catherine Struve has put together a thoughtful guide on AI and attribution that's worth reading:

Bias

AI models reflect the biases present in their training data. This is well-documented and worth keeping in mind — especially in contexts that affect people directly: hiring decisions, admissions-related work, student evaluations, or any process where fairness matters. AI output can be a useful input, but it shouldn't be the sole basis for consequential decisions about people.

Penn Law Exam Policies

AI policies for exams are set by individual faculty and administered through the Registrar's office. The pedagogy portal has current guidance on exam AI policies, including model syllabus language and the different policy tiers available:

Penn AI Policy Sources

The authoritative sources, with PCL-specific guidance first:

• Penn Law ITS — AI Tools & Guidance — PCL-specific approved tools, with school-specific user guides for Copilot Chat, Zoom AI Companion, ChatGPT, and Harvey (Penn Law access only)
• Penn Generative AI Tools & Resources — Penn ISC's central list of approved AI tools and their data-classification mappings
• Penn Data Risk Classification — the underlying framework for what counts as Low, Moderate, and High Risk
• Statement on Guidance for the Penn Community on Use of Generative AI — the university-wide policy on transparency, data privacy, and security
• Microsoft Copilot Chat FAQ — activation and use details for Penn's Copilot deployment
• ChatGPT EDU FAQ — account access and data handling for Penn's ChatGPT deployment

Specific policies vary by context. Research use, classroom use, and administrative use may each have different considerations. When a situation doesn't fit neatly into the guidance above, reach out and we'll think it through.

For teaching-specific AI resources — syllabus language, exam policies, classroom tools, and pedagogy guides — see the companion portal:

Curriculum

AI is integrated into the 1L Legal Practice Skills program — students engage AI tools as part of foundational legal training, not as an elective. Faculty across the curriculum have also experimented with AI-integrated assignments, simulations, and new assessment approaches.

Technology Partnerships

We have institutional access to a growing set of AI tools — Claude, arriving school-wide for 2026–27 and integrated into the 1L curriculum; the legal-specific platforms Harvey and Legora; and ChatGPT EDU for faculty and staff — supporting AI use across teaching, research, and administration. Details and access info are on the Getting Started tab.

Faculty Support

Workshops on AI use cases, pedagogy, and tool adoption. A faculty AI toolkit with practical guidance and best practices. Regular communications keeping faculty current on developments. I coordinate all of this — reach out if you want to get involved.

Student Programs

The Madhani Legal Tech Fellowship supports students building legal technology ventures — an established entrepreneurial pathway connecting law students to the legal tech ecosystem.

Faculty Research

Multiple faculty are conducting active research on AI and law — spanning governance, intellectual property, regulatory frameworks, and the structure of legal work.

For teaching-focused scholarship on AI and legal education, see the Reading & Research section on the Pedagogy Resources portal.

Below are the sources I follow most closely and recommend to colleagues. This is how I keep up — and honestly, keeping up is half the challenge.