Claude for Teachers Just Launched. Connect These Three Things First (and Not Your Gradebook)

Teacher group chats lit up this week, and for once the news deserved it. AI agents, the kind that do multi-step work instead of answering prompts, just became free classroom infrastructure. Before you connect everything with an account, here is the ten-minute version of what changed, the safe connection order, and the one door to leave closed for now.

What actually launched, and why it is different from a chatbot

An agent plans and executes work across connected tools; a chatbot answers one prompt at a time. Claude for Teachers connects to Learning Commons, which means academic standards for all fifty states plus the smaller competencies beneath each standard and the order students typically learn them, along with trusted curricula like OpenSciEd and Illustrative Mathematics, and edtech connectors including ASSISTments, Brisk Teaching, and Canva Education. Ask it for a unit and it arrives already aligned rather than needing to be checked line by line. Google, meanwhile, has put Gemini into Classroom at no cost for Workspace for Education schools. For three years the differentiating teacher skill was prompting, coaxing a generic model into standards-aligned output. That skill was just automated. What is scarce now is knowing what to delegate, specifying it well, verifying it honestly, and owning what ships, and nobody trained teachers for that, because until this week nobody needed to.

Should I connect Claude to everything it offers?

No. Connect in three tiers, and the order is the whole safety model. First, standards and curriculum connectors: they read nothing about your students and only make output better. Connect these on day one; this is where the launch genuinely shines. Second, design and creation tools: they touch your content, not student records, so keep grants draft-only where offered and publish yourself. Third, and this is the deliberate one: anything that reads rosters, grades, submissions, or an LMS waits weeks, not hours, until you have answered five questions: what does this connector read, what can it write or send, what is retained and where, what has my district actually signed with this vendor, and what is the smallest scope that does the job. A connector that reads your gradebook is a student-data decision even when the chat window feels casual.

Is it safe to put student data into a free teacher account?

Not yet, and this is the distinction that will separate the careful from the cautionary tales this fall. There are three lanes. Consumer AI accounts: no student data, ever, same rule as always. Verified-educator tiers, which is what a free teacher account is: better terms than consumer, but YOUR DISTRICT signed nothing, so student data stays out until your district reviews the vendor's terms and says otherwise in writing. District-contracted platforms with a signed data-privacy agreement: student data may flow within the agreement's scope, and only there. Verified-you is not contracted-district. And IEP or 504 content sits above all three lanes: it moves only where a DPA explicitly covers it and special-education leadership has signed off. When an agent offers to pull past assessment data and draft individualized plans overnight, the technology being able to is not the same as your authorization to let it.

How do I use an agent without shipping its mistakes?

Delegate, verify, own. Delegate with a brief, not a prompt: the outcome, your constraints, your materials, and a checkpoint where the agent stops and shows you the outline before drafting everything, because judgment spent at the outline costs minutes and judgment spent after day four costs a rebuild. Verify by risk: full reads for anything mathematical, factual, parent-facing, or safety-adjacent; honest spot-checks elsewhere; and one rule that keeps sampling honest: a failed spot-check escalates to a full audit. Own everything that ships: your name, your license, your call. Agents do not fail the way colleagues fail. They fail silently, confidently, and in bulk, which means the scary error is not the wrong answer you catch on Tuesday; it is the subtly miscalibrated reading level shipped daily for six weeks because the tool "proved itself" in week one.

Want the complete playbook?

The full discipline is The Agentic Classroom, Book 1: When AI Stops Chatting and Starts Working: the 22-page field manual with the delegation-brief format, the risk-weighted verification table, context engineering in five layers, the three-lane student-data map, eight workflows, and the 90-day adoption plan, plus the editable Agent-Ready Context Pack, the 20-brief Agent Workflow Library, and the printable Delegate-Verify-Own Protocol for your wall and your principal. Tool-agnostic by design: it works on every agentic platform, including the ones that do not exist yet.

→ Get The Agentic Classroom, Book 1 ($29.99)

Frequently asked questions

Is Claude for Teachers really free?
Yes: verified US K-12 educators get a year of free access, with sign-up open through June 30, 2027, per Anthropic's July 14, 2026 announcement. Free access is real and worth taking; just remember that a free teacher account is not a district data-privacy agreement.

What should I connect first?
Standards and curriculum connectors (like Learning Commons sources): they touch no student data and immediately improve output. Design tools second, draft-only. Anything reading rosters, grades, or an LMS waits for the five connector questions and your district's written answer.

Can I put student names or work into Claude for Teachers or Gemini in Classroom?
Not on the strength of a free teacher account. Student data belongs only in platforms your district has contracted under a data-privacy agreement, within that agreement's scope. Ask your tech director what has actually been signed; being the teacher who asks is a good look.

Do prompting skills still matter?
The recipe-style prompting of the last three years matters much less: alignment and structure are becoming native. What compounds now is the layer above: delegation briefs, verification habits, a context system the agent works from, and clean data judgment. That layer is portable across every platform.

What about my district: what should leadership be doing?
Reviewing vendor terms, deciding which tools get data-privacy agreements, and giving teachers written lane rules before the school year starts. That side of the story is Book 2 of the series, The District AI Playbook, coming soon; teachers piloting responsibly now (logs kept, protocol printed) will be the people those committees recruit.