Wrestling with AI: plain-text version

This is the same page as Wrestling with AI, without color coding. Each passage written primarily by a human is labeled “Written by a human.” Everything else was written primarily by Claude, relying on human input.

Written by a human

This site was planned and drafted by engaging a large language model, Claude, by Anthropic, used in the Claude desktop app (Cowork). A human wrote a detailed project plan (about 3,000 words), which included naming concerns with AI and attempting to encourage Claude to incorporate a critical approach in its output. Claude was prompted, in an interactive process with human feedback, to draft plans, research summaries, page text, code, and the version 1 brain drawings. The website will go no further until and unless a team of humans, with various kinds of expertise and perspectives, decides it is worth pursuing, including checking science claims.

Written by a human

The human behind this website is deeply troubled by the impact large language models have on our environment, politics, economics, creativity, and interpersonal relationships. This website was an experiment in playing with AI to see what was possible.

Written by a human

The issues with AI are well documented, including that it replicates and reflects biases in its training data and design, its use has a devastating impact on the environment, and creating with it blurs lines of authorship. For useful and interesting research on AI, visit DAIR (Distributed AI Research Institute).

[Written by a human:] Although the initial instructions, when this project began, included a request to track the tokens (the small chunks of text an AI model reads and writes, which can be a proxy for estimating the cost of the AI use), the tracking didn’t happen. When asked why it did not happen, Claude responded that the chat app doesn’t show a running token count, so tracking it would have taken a deliberate step at the end of each session and “nobody was assigned to do it.” Claude’s best estimate (completed retroactively) is [End of human-written text.] that this project took roughly 100 million tokens, almost all of them the AI re-reading the growing conversation at each step, including about 400,000 tokens of text the AI wrote. Only one of the three working sessions could be measured: it used about 44 million tokens, including about 155,000 written by the AI. The other two are estimated from their length.

What does that mean in dollars and energy?

Tokens don’t translate neatly into money or electricity, and Anthropic doesn’t publish energy figures for its models, so these are rough translations.

Dollars. If a developer had paid Anthropic’s published prices for this model ($4 per million tokens read for the first time, $0.20 per million tokens re-read, and $20 per million tokens written), this project would have cost roughly $40, and almost certainly between $25 and $60 (Anthropic, n.d.). (Unchecked by a person; AI research only.) That’s not what the person building this site paid: the AI was used through a subscription plan, not billed per token.

Energy and water. Google reports that a typical text request to its Gemini AI uses about 0.24 watt-hours of electricity and about 0.26 milliliters of water, roughly five drops (Vahdat & Dean, 2025). (Unchecked by a person; AI research only.) An independent estimate for ChatGPT puts a typical question at about 0.3 watt-hours, but close to 40 watt-hours when the AI has to read about 100,000 tokens of material at once (You, 2025). (Unchecked by a person; AI research only.) This project sent the AI several hundred requests, most of them very long. Our best guess is that it used somewhere between 0.1 and 3 kilowatt-hours of electricity, most likely between half a kilowatt-hour and 1 kilowatt-hour. One kilowatt-hour is about what a laptop uses running for a full day, or a microwave running for an hour. Using Google’s water figures, 1 kilowatt-hour would mean roughly 1 liter of water for cooling. Other researchers count more, for example the water used to generate the electricity.

These are estimates built on other companies’ numbers for other AI models, so treat them as a sense of scale, not a measurement.

Trade-offs we made

Building version 1 meant choosing between goals that pull against each other. We wanted the site to exist now, without a budget, so we used AI for work that people should do, such as drawing the brain scans and researching the science, and we labeled that work instead of hiding it. We used images from Plants vs. Zombies because we suspect students recognize them, even though that means part of the site can’t be openly licensed. We didn’t ask students about the value of this site before we built it, and we haven’t yet asked students to evaluate it. We simplified the science, showing two zombies, one view of the brain, and a few regions, which makes it easier to learn but less complete. We used a spooky font only for a few words, so the rest stays easy to read. And we chose to publish an unreviewed draft in public, with every unchecked claim labeled, because being open about our mistakes seemed better than waiting until we had none.

What AI did here, and what people should do

Written by a human

The following table was created by Claude in response to a prompt about what would be better to have humans create and directing it to various sources that critique AI.

Useful jobs for AIBetter done by people
Drafting site code and templates for people to reviewArtwork and illustrationVersion 1: brain scans are AI-drawn and not yet reviewed.
Checking pages against accessibility rulesAccessibility testing with disabled usersVersion 1: not yet done.
First drafts of image descriptions (alt text)Final say on every scientific claimVersion 1: AI drafted the brain reports; no person has checked the science yet.
Organizing citations and checking APA formatChoosing which zombies people actually know (by asking students)Version 1: not yet done; the team chose two zombies for the prototype.
Turning design notes into wireframes and plansAdding human voice and toneVersion 1: the field notes are plain observations, and the one joke was drafted by AI.
Summarizing feedback, with personal details removedDecisions about values, framing, and trade-offs

Who else should be at the table

Written by a human

The following table was created by Claude in response to a prompt about who should be on the design team and providing it a memo that included describing the kind of feedback this site should withstand.

RoleWhy we need themStatus
Neuroscientist or neuroanatomistChecks every brain claim and image before we share widely.Not yet
Disabled students and accessibility testersReal-world testing with screen readers, keyboard-only use, low vision, and cognitive access.Not yet
Illustrator, ideally a CUNY studentReplaces the AI-drawn brain scans and site art.Not yet
Copyright or scholarly communications librarianReviews our use of game images and our Creative Commons license.Not yet
Game studies or media studies scholarReviews how we portray the game, its fans, and zombie tropes, including the zombie’s roots in Haitian history and religion.Not yet
Instructional designer or OER librarianAligns the site with course goals and helps share it as an open resource.Not yet
Intro Psych students as testersTell us what’s confusing, boring, or funny.Not yet