Spring 2026 | Wednesdays 6:30-8:30
CUNY Graduate Center
Michelle McSweeney | michelleamcsweeney@gmail.com
https://github.com/michellejm/Agentic_AI_Spring26
This course explores the emergence of agentic artificial intelligence—AI systems with access to tools that are designed to operate with varying degrees of autonomy in complex, dynamic environments.
As these systems are rapidly adopted across industries, it marks a fundamental shift from computers-as-tools used by humans to computer programs that no longer need human input to accomplish tasks. Though there are a wide range of definitions for what constitutes an “agent”, the core idea is centered on autonomy and the ability to direct tasks. As AI evolves from isolated tools into systems capable of independent action (with “agency”), understanding the technical foundations, design constraints, ethical questions, and social risks becomes increasingly vital for shaping agents to mirror the world that we want. By bringing a critical lens to both the technology and its application, the goal of this course is for you to confidently engage with—and shape—the future of agentic AI. You will architect and build an agentic workflow leveraging at least one LLM decision point, and use that experience along with foundational readings to develop an informed, grounded perspective on agentic AI systems and the cultural/social questions they surface.
This course will be taught using Databricks as the primary development platform though you are welcome to use any LLM orchestration method you prefer.
There are two parts to this course: technical and social. These are equally important and the line between them is largely artificial.
- The focus of the first half will be technical. You will design, create, and refine an agent by the midway point of the course. You will explore different low-code and no-code ways of setting them up, and you will gain technical familiarity with how Agents are built.
- The focus of second half will be social/humanistic. You will still keep working on your project, but our attention will shift to considering some of the major debates about the impacts of AI Agents on society and culture.
Notes:
- LLM-based agents are so new that there is no widely-accepted methodology for how they should be designed and built. There are many methodologies, approaches, and platforms, and by taking this course and engaging in the process, you are shaping these norms.
- It is entirely possible that something new may come out during this course that completely changes our understanding of how Agents [should] work. If that happens, we will learn about it together.
Please use one/some. I don’t care which one, and I don’t expect attribution. To get something decent, you have to do the thinking. To get something well written, you have to do the writing. LLM’s will give you input and are an invaluable tool for working out ideas, phrasing, and organization, but they cannot do the hard work of thinking. That said, they are an excellent sounding board and useful tool. Used well, they will make your writing and organization better and clearer. Used poorly and you will simply reiterate trite ideas and language regressed to the mean. It is impossible to form an informed opinion without experience, so you need to use LLMs for some part of your process. However, out of courtesy of our relationship, please do not have an LLM write your emails to me unless you really need help.
Labs and examples will be designed with Databricks free edition and Langchain. These platforms are not required. We are using it because they are great technologies that makes building low-code agents extremely simple. However, if you want to use another platform, you can use anything where you can make an agent. This can be pure python with a Mistral model, crew ai, Anthropic’s Agent Builder, or anything else (don’t worry if you have no idea what any of those things are - you’ll soon be familiar with the landscape).
You will build an AI agent and evaluate it. This can be an ‘agentic system’, a workflow (there is a distinction, but it’s too academic to be practical), or a multi-agent supervisor. You will have to invent a problem that is sufficiently complex and yet atomizable to justify using an agent. Agents are not the right tool for every problem. Problems will be due very early in the semester as you will need time to work on designing the right flow.
A good problem for an agent has these properties:
- Requires decision-making under uncertainty (not deterministic)
- Involves multiple steps, tools, or environments
- Benefits from autonomy and adaptation
- Has feedback loops (the agent can learn from results)
Be as creative as you like, or as practical as you like. Some general examples:
- [Fill in the blank] recommender that processes user input to generate a search query and then either searches the internet for a recommendation or asks for more information.
- Research Assistant that takes a question, performs a focused web or document search, extracts key facts, summarizes them, and responds with sources.\
- Keyword Search Agent that extracts keywords from [fill in the blank] and then does a focused internet search for [research papers/news articles/etc.].
Some general but unrealistically ambitious examples.
- Continuous competitive intelligence agent that monitors news, filings, and social signals to alert a company to emerging threats and opportunities.
- Personal life-logistics agent that schedules, reschedules, negotiates conflicts, and optimizes across health, work, and family constraints.
- Scientific discovery agent that proposes hypotheses, designs experiments, evaluates results, and refines future experiments in a closed loop.
- Autonomous data analysis agent that cleans raw datasets, runs exploratory analysis, revises hypotheses, and produces stakeholder-ready reports.
- Content creation agent that reviews input files, searches the internet, summarizes sources, and drafts an essay.
These are very general. Interesting problems tend to be very specific, and the more specific you are, the easier it will be to set up a constrained workflow. We will work on this together – there are two 1:1 sessions to discuss your project via Zoom.
Projects will be due at the end of the semester. We will have a “poster session” style presentation to showcase projects on the last day.
Projects have three pieces:
- A proposal (30%). Proposals should include:
- A problem statement
- A clear description of the problem or task your agent is intended to address.
- An explanation of why this problem justifies an agentic approach (as opposed to a script, chatbot, or single model call).
- A proposed design, indicating
- The decision points, including:
- What decision is being made at each point (e.g., planning, routing, evaluation, delegation).
- Whether the decision is deterministic or non-deterministic
- Explanation of tool use
- What tools can be called at each decision point.
- Why those tools
- Feasibility analysis
- Evidence that the project is technically achievable within the course timeline (propose what tools you will use)
- Clear articulation of scope: what you will build and what you are intentionally leaving out.
- The decision points, including:
- A problem statement
- The technical artifact (20%)
- The technical implementation (AI should help you with this)
- The decision points working
- A result or output that is generated
- The final presentation
- A reflection (50%)
- Description of the design, goal, and decision points
- Clear explanation of your agent’s goal, structure, and decision points.
- Description of the decisions you made along the way.
- Reflection on design tradeoffs and limitations.
- Social/cultural/humantistic evaluation.
- Situate your agent within a larger social or cultural context
- Consider implications at:
- An individual level (e.g., cognition, responsibility, dependency), and/or
- A societal or scale level (e.g., labor, institutions, power, norms)
- Ground your analysis in:
- Course readings,
- Historical or philosophical discussions of agency, or
- Contemporary debates around AI and autonomy.
- Your own review of your agent
- Your assessment of:
- The agent’s usefulness or effectiveness,
- Whether it achieved its stated goals,
- Its significance as a symbol or example of broader agentic trends.
- This evaluation should be grounded in a broader context, not purely personal opinion.
- Your assessment of:
- Description of the design, goal, and decision points
Strong projects will:
- Use agents intentionally to solve a complex problem
- Leverage decision making and articulate the decisions clearly
- Show awareness that agentic systems (and all technologies) are not just tools, but are situated in social systems and their presence affects the system.
- Treat agents as objects of reflection, not just optimization.
Labs are given ~weekly. They will be graded on completion and are worth 25% of your grade. Some are more technical than others. Submit them via email. If you can’t get one to work, explain what your set up is, what the problem is, and what you tried. You can do this in writing or a screen recording video. You need to either get it to work or clearly explain your steps in a way that I could reproduce the problem and troubleshoot it.
The readings/lab should be completed before the class session they are listed for.
| W | Date | Topic | Readings | Due |
|---|---|---|---|---|
| 1 | 1/28 | Introduction | (optional) Intelligent Agents: Theory and Practice – Wooldridge & Jennings, 1995 (optional) Agency – Sections 1 & 2 (Stanford Encyclopedia of Philosophy) |
Sign up for Databricks Free Edition and Langsmith (free) |
| 2 | 2/4 | Brief intro to LLMs | Single Tool Agent Lab | |
| 3 | 2/11 | Defining Agents, Agent Taxonomy, Tools and Tool Calling | Building Effective Agents (Anthropic)** Huggingface: What is an Agent (optional) AI Agents vs. Agentic AI (optional) OpenAI on Tools |
Prompt Engineering Lab |
| 4 | 2/18 | MCP, Problems for Agents, Designing an Agentic System | MCP Introduction (optional) Databricks MCP Docs |
Reasoning Mini-Lab and PB&J Lab |
| 5 | 2/25 | Problems for Agents, Designing an Agentic System | Practical Guide for Production-Grade Agentic AI Workflows (Section 3 only)** Designing a Successful Agentic AI System (HBR – library access) |
Goodreads Lab |
| 6 | 3/4 | Context, Memory, and Learning | Architecting Efficient Context-Aware Multi-Agent Framework (optional) Cognitive Architectures for Language Agents How We Built Our Multi-Agent Research System A Self-Improving Coding Agent |
Problem Statement + Multi-Agent Lab |
| 7 | 3/11 | Project Design Review (Zoom) | 1:1 project meetings | Project Design (due 8pm on 3/10) |
| 8 | 3/18 | Agent Evaluation and Governance | Best Practices for Agentic Benchmarks Survey on LLM-as-Judge LLM-as-a-Judge Explained Agentic AI: Comparing Open-Source Frameworks (optional) LangChain Quickstart (optional) DSPy Docs AI Agents in Action (WEF) |
RLHF Lab |
| X | SKIP | Agency Since 1950 | Pick one: (a) Newell & Simon on Symbolic AI (b) Could Symbolic AI Unlock Human-Like Intelligence? (c) McCarthy – Programs with Common Sense (d) Minsky & Papert – Society of Mind (optional) ReAct Paper Self-Prompting LLMs Fully Autonomous AI Agents Should Not Be Developed |
NA |
| 9 | 3/25 | Agents as Workers / Teams (Trust) | Steam, Steel, and Infinite Minds How Do AI Agents Do Human Work? Future of Work with AI Agents** |
Eval Lab |
| — | 4/1 | No Class | ||
| — | 4/8 | No Class | ||
| 10 | 4/15 | AI Anthropomorphism / Human-Agent Relationships / Agents in Education | Selected readings (TBD by vote) | TBD |
| 11 | 4/22 | Project Consultations (Zoom) | Project Prototype | |
| 12 | 4/29 | Agents as Thinking Machines | (optional) Turing (1950) Reasoning in LLM-based Agents What is a Reasoning Model?** |
Work on Projects |
| 13 | 5/6 | Agents and Personhood | (optional) Frankfurt (1971) Anthropomorphic Conversational Agents** Theory of AI Personhood Artificial Agents – Personhood in Law |
Work on Projects |
| 14 | 5/13 | Presentations |
** Most essential readings
Supplemental Readings (I will keep adding to this list):
- Russel and Norvig (2020). Artificial Intelligence: a modern approach.