The author explained that she treats artificial intelligence purely as a practical research tool, similar to a digital assistant. She said she uses it for tasks such as quick background queries, organizing research, or checking facts—not for generating the literary text itself.
The episode resonated widely because it touches a central tension in modern publishing: the difference between AI‑assisted workflow and AI‑generated writing.
Many writers already use digital tools to support their process—search engines, archives, note‑organizing apps, or translation tools. Language models can extend this role by helping with research, brainstorming, or summarizing information.
But using AI to generate substantial portions of prose raises deeper questions:
Publishing organizations have increasingly warned about these issues. The Authors Guild, for example, says generative AI capable of producing books poses a significant threat to writers if it replaces human authorship, even while acknowledging that many writers use AI tools for research, brainstorming, or organization.
Tokarczuk’s reputation as a literary stylist made the misunderstanding particularly sensitive. Her novels—such as Flights and The Books of Jacob—are known for distinctive voice and intricate structure, qualities readers strongly associate with human authorship.
As a result, ambiguous remarks about AI were enough to trigger fears that a major novelist might have crossed from using AI as a research aid to using it as a ghostwriter.
Her clarification underscored that, at least in her own work, the creative act remains human.
The incident illustrates how quickly AI discussions can escalate in the cultural sphere. For many writers, the technology is simply another tool in the research process. For others, it represents a potential shift in how literature is created and credited.
Tokarczuk’s response ultimately drew a clear boundary: AI may help gather information or test ideas, but the storytelling—the voice, structure, and final words of the novel—remains her own.
Comments
0 comments