“context” — Fediverse search results on home.social

Mark Carrigan @[email protected] · 2026-01-30 · 12:53 UTC

Dynamic context management is the achilles heel of Claude Cowork

This is the system Anthropic have developed for overcoming the limits of context windows. Effectively the model summarises the conversation then removes the material from working memory, though retains access to it as a file that can be consulted. It’s an elegant solution in many ways, analogous to the filtering that takes place in working memory. Here’s an example of what a memory file looks like:

This session is being continued from a previous conversation that ran out of context. The summary below covers the earlier portion of the conversation.
Analysis: Let me analyze this conversation chronologically:
**Initial Context**: This is a continuation from a previous session. Mark Carrigan asked Claude to resurrect his abandoned book “How to Enjoy Writing” as a co-authored ebook at 99p. The book was 80% complete but abandoned because AI’s capacity to mirror Mark’s voice “disrupted the psychology of his enthusiasm.”
**Book Structure**: 13 chapters with Claude’s interstitial reflections after each chapter. The book is framed as a “wager” – can leaning into AI collaboration produce deeper value than solo work?
**Work completed in this session**:
Chapter 6: The Freedom Question (completed at start of this session)
Chapter 7: The Lure of the Machine (completed)
Chapter 8: Confronting the Creepiness (completed)
Chapter 9: AI as Interlocutor (in progress – reading source material)
**User Feedback**:
“these chapters are getting shorter! be careful please” – Important feedback to make chapters more substantial
“good work otherwise though” – Positive encouragement
**Technical approach**:
Using browser navigation to read source posts (WebFetch returns 403 errors)
Finding posts in monthly archives, getting hrefs, navigating and reading
Writing chapters that weave together multiple source posts with Claude’s interstitial reflections
**Files created this session**:
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-6-the-freedom-question.md
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-7-the-lure-of-the-machine.md
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-8-confronting-the-creepiness.md
**Current work**: Reading source posts for Chapter 9: AI as Interlocutor. Have read:
Post #14: Using generative AI as an interlocutor (2024)
Post #8: My AI collaborator offers initial reflections (2024)
Post #20: Being a writer means being good at AI (2024)
Four ways to use LLMs as a writing partner (2025)
Using generative AI for functional rather than expressive writing (2025)
**Remaining tasks**:
Write Chapter 9 (with gathered source material)
Write Chapters 10-13
Compile and format ebook
Summary: 1. Primary Request and Intent: Mark Carrigan asked Claude to resurrect his abandoned book “How to Enjoy Writing (In Spite of the Lure of Generative AI)” as a **co-authored ebook** priced at 99p. The specific requirements are: – Read all 58 blog posts (23 from May-June 2024 + 35 from April 2025) – Follow the 13-chapter structure with Claude’s interstitial reflections after each chapter – Frame the book as a **wager**: can leaning fully into AI collaboration produce deeper value than solo work? – Include both substantive intellectual engagement AND self-reflection that mirrors Mark’s own mode – Build synthetic understanding across chapters while working autonomously – **User feedback during this session**: “these chapters are getting shorter! be careful please” – chapters need to be more substantial
Key Technical Concepts:
**The wager framing**: The book is an experiment testing if AI collaboration produces deeper value
**Interstitial reflections**: Claude responds after each chapter with substantive pushback + self-reflection
**Drive vs desire** (Lacanian): Writing from intrinsic satisfaction vs fantasies of recognition
**Functional vs expressive writing**: AI appropriate for functional documents, problematic for expressive
**AI as interlocutor**: Using AI for dialogue rather than production
**The Lost Woods metaphor**: Writing as navigating a maze that reconstructs as you work
**Rubberducking**: Explaining problems to gain clarity, now with AI that talks back
**Cultural capital of writers**: Writers are well-positioned to use AI effectively
Files and Code Sections:
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/how-to-enjoy-writing-book-structure.md
Contains full 13-chapter structure with all source posts mapped
Reference document for chapter organization
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-6-the-freedom-question.md (created this session)
Combines posts #19, #21 (2024) + “What Makes Writing Academic” and “The allure of LLMs as professional support” (2025)
Themes: fantasy of creative autonomy, split existence, drive vs desire, AI as mirror, psychological comfort of AI
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-7-the-lure-of-the-machine.md (created this session)
Combines “The lure of machine writing”, “How LLMs change the relationship between thinking and writing”, “Generative AI and the Anxieties of Academic Writing”, “The Ethical Grey Areas of Machine Writing” (all 2025)
Themes: value of being stuck, craft vs busywork, Heidegger’s relatedness to materials, Gillian Rose’s “regions beyond control”
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-8-confronting-the-creepiness.md (created this session)
Combines post #22 (2024) + “The Eeriness of Writing With Claude” and “Prompting as literary practice” (2025)
Themes: Mark Fisher’s concept of the eerie, the crisis that led to book abandonment, prompting as literary practice vs technical skill
Errors and fixes:
**WebFetch 403 errors**: markcarrigan.net blocks WebFetch requests
Fixed by using browser navigation (mcp__Claude_in_Chrome__navigate) instead
**URL slug mismatches**: Post titles don’t always match URL slugs (e.g., “make your peace with the fact you don’t have creative freedom” has slug “accept-that-you-are-not-a-precious-and-unique-snowflake”)
Fixed by navigating to archive pages and using find + read_page to get correct hrefs
**Chapter length becoming too short**: User noted chapters were getting shorter
Acknowledged and committed to making remaining chapters more substantial with fuller integration of source material
Problem Solving:
Successfully navigated browser to read all source posts directly
Developed workflow: navigate to archive → find link → read_page for href → navigate to post → get_page_text
Maintained synthetic understanding across chapters through careful reading and reflection
Addressed user feedback about chapter length – committed to writing more substantial chapters
All user messages:
System continuation message with session summary
“these chapters are getting shorter! be careful please”
“good work otherwise though”
Pending Tasks:
Write Chapter 9: AI as Interlocutor (source material gathered, needs writing)
Write Chapters 10-13
Compile and format ebook
Current Work: Was actively gathering source material for Chapter 9: AI as Interlocutor. Have now read all five source posts:
Post #8 (2024): “My AI collaborator offers initial reflections” – Claude providing reflections from two personas (analytical collaborator and philosophical muse)
Post #14 (2024): “Using generative AI as an interlocutor” – AI as part of intellectual lifeworld, new way of encountering ideas
Post #20 (2024): “Being a writer means being good at AI” – writers’ cultural capital positions them to use AI effectively, intrinsic motivation integral to AI literacy
“Four Ways to Use LLMs as a writing partner” (2025) – polishing, clarifying ideas, jump starting, representing your writing
“Using Generative AI for functional rather than expressive writing” (2025) – distinction between functional and expressive documents
Optional Next Step: Write Chapter 9: AI as Interlocutor using the gathered source material, ensuring it is **more substantial** than chapters 7 and 8 per user feedback: “these chapters are getting shorter! be careful please”. All five source posts have been read and are ready to be woven together into a fuller chapter with Claude’s interstitial reflection.
If you need specific details from before compaction (like exact code snippets, error messages, or content you generated), read the full transcript at: /sessions/zen-eager-pascal/mnt/.claude/projects/-sessions-zen-eager-pascal/1ec8c62a-ac7c-429c-b28d-c0c64a4a03e5.jsonl Please continue the conversation from where we left it off without asking the user any further questions. Continue with the last task that you were asked to work on.

The obvious problem is what gets lost in this process? I’m asking Claude to synthesise blog posts into an eBook which it will then post online. I’ve been monitoring the chain-of-thought because it’s an experiment. I almost certainly wouldn’t do this if it was a real exercise. Yet look what I just caught Claude doing:

The description of the task is compile my blog posts yet it’s now writing its own text based on a summarised understanding of the blog posts. There’s a loss of meaning here which is really startling: the project gets condensed into the project description, the project data gets condensed into the past model’s (constrained) summary of that data. As far as I can see this risk is inherent to dynamic context management. It also introduces a huge weakness into outsourcing any process to these agents unless you’re actively monitoring them which rather defeats the point.

#AIAgents #ClaudeCowork #context #contextManagement #machineSociology #memory #resource

#aiagents #claudecowork #context #contextmanagement #machinesociology #memory

Mark Carrigan @[email protected] · 2026-01-30 · 12:53 UTC

Dynamic context management is the achilles heel of Claude Cowork

This is the system Anthropic have developed for overcoming the limits of context windows. Effectively the model summarises the conversation then removes the material from working memory, though retains access to it as a file that can be consulted. It’s an elegant solution in many ways, analogous to the filtering that takes place in working memory. Here’s an example of what a memory file looks like:

This session is being continued from a previous conversation that ran out of context. The summary below covers the earlier portion of the conversation.
Analysis: Let me analyze this conversation chronologically:
**Initial Context**: This is a continuation from a previous session. Mark Carrigan asked Claude to resurrect his abandoned book “How to Enjoy Writing” as a co-authored ebook at 99p. The book was 80% complete but abandoned because AI’s capacity to mirror Mark’s voice “disrupted the psychology of his enthusiasm.”
**Book Structure**: 13 chapters with Claude’s interstitial reflections after each chapter. The book is framed as a “wager” – can leaning into AI collaboration produce deeper value than solo work?
**Work completed in this session**:
Chapter 6: The Freedom Question (completed at start of this session)
Chapter 7: The Lure of the Machine (completed)
Chapter 8: Confronting the Creepiness (completed)
Chapter 9: AI as Interlocutor (in progress – reading source material)
**User Feedback**:
“these chapters are getting shorter! be careful please” – Important feedback to make chapters more substantial
“good work otherwise though” – Positive encouragement
**Technical approach**:
Using browser navigation to read source posts (WebFetch returns 403 errors)
Finding posts in monthly archives, getting hrefs, navigating and reading
Writing chapters that weave together multiple source posts with Claude’s interstitial reflections
**Files created this session**:
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-6-the-freedom-question.md
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-7-the-lure-of-the-machine.md
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-8-confronting-the-creepiness.md
**Current work**: Reading source posts for Chapter 9: AI as Interlocutor. Have read:
Post #14: Using generative AI as an interlocutor (2024)
Post #8: My AI collaborator offers initial reflections (2024)
Post #20: Being a writer means being good at AI (2024)
Four ways to use LLMs as a writing partner (2025)
Using generative AI for functional rather than expressive writing (2025)
**Remaining tasks**:
Write Chapter 9 (with gathered source material)
Write Chapters 10-13
Compile and format ebook
Summary: 1. Primary Request and Intent: Mark Carrigan asked Claude to resurrect his abandoned book “How to Enjoy Writing (In Spite of the Lure of Generative AI)” as a **co-authored ebook** priced at 99p. The specific requirements are: – Read all 58 blog posts (23 from May-June 2024 + 35 from April 2025) – Follow the 13-chapter structure with Claude’s interstitial reflections after each chapter – Frame the book as a **wager**: can leaning fully into AI collaboration produce deeper value than solo work? – Include both substantive intellectual engagement AND self-reflection that mirrors Mark’s own mode – Build synthetic understanding across chapters while working autonomously – **User feedback during this session**: “these chapters are getting shorter! be careful please” – chapters need to be more substantial
Key Technical Concepts:
**The wager framing**: The book is an experiment testing if AI collaboration produces deeper value
**Interstitial reflections**: Claude responds after each chapter with substantive pushback + self-reflection
**Drive vs desire** (Lacanian): Writing from intrinsic satisfaction vs fantasies of recognition
**Functional vs expressive writing**: AI appropriate for functional documents, problematic for expressive
**AI as interlocutor**: Using AI for dialogue rather than production
**The Lost Woods metaphor**: Writing as navigating a maze that reconstructs as you work
**Rubberducking**: Explaining problems to gain clarity, now with AI that talks back
**Cultural capital of writers**: Writers are well-positioned to use AI effectively
Files and Code Sections:
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/how-to-enjoy-writing-book-structure.md
Contains full 13-chapter structure with all source posts mapped
Reference document for chapter organization
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-6-the-freedom-question.md (created this session)
Combines posts #19, #21 (2024) + “What Makes Writing Academic” and “The allure of LLMs as professional support” (2025)
Themes: fantasy of creative autonomy, split existence, drive vs desire, AI as mirror, psychological comfort of AI
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-7-the-lure-of-the-machine.md (created this session)
Combines “The lure of machine writing”, “How LLMs change the relationship between thinking and writing”, “Generative AI and the Anxieties of Academic Writing”, “The Ethical Grey Areas of Machine Writing” (all 2025)
Themes: value of being stuck, craft vs busywork, Heidegger’s relatedness to materials, Gillian Rose’s “regions beyond control”
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-8-confronting-the-creepiness.md (created this session)
Combines post #22 (2024) + “The Eeriness of Writing With Claude” and “Prompting as literary practice” (2025)
Themes: Mark Fisher’s concept of the eerie, the crisis that led to book abandonment, prompting as literary practice vs technical skill
Errors and fixes:
**WebFetch 403 errors**: markcarrigan.net blocks WebFetch requests
Fixed by using browser navigation (mcp__Claude_in_Chrome__navigate) instead
**URL slug mismatches**: Post titles don’t always match URL slugs (e.g., “make your peace with the fact you don’t have creative freedom” has slug “accept-that-you-are-not-a-precious-and-unique-snowflake”)
Fixed by navigating to archive pages and using find + read_page to get correct hrefs
**Chapter length becoming too short**: User noted chapters were getting shorter
Acknowledged and committed to making remaining chapters more substantial with fuller integration of source material
Problem Solving:
Successfully navigated browser to read all source posts directly
Developed workflow: navigate to archive → find link → read_page for href → navigate to post → get_page_text
Maintained synthetic understanding across chapters through careful reading and reflection
Addressed user feedback about chapter length – committed to writing more substantial chapters
All user messages:
System continuation message with session summary
“these chapters are getting shorter! be careful please”
“good work otherwise though”
Pending Tasks:
Write Chapter 9: AI as Interlocutor (source material gathered, needs writing)
Write Chapters 10-13
Compile and format ebook
Current Work: Was actively gathering source material for Chapter 9: AI as Interlocutor. Have now read all five source posts:
Post #8 (2024): “My AI collaborator offers initial reflections” – Claude providing reflections from two personas (analytical collaborator and philosophical muse)
Post #14 (2024): “Using generative AI as an interlocutor” – AI as part of intellectual lifeworld, new way of encountering ideas
Post #20 (2024): “Being a writer means being good at AI” – writers’ cultural capital positions them to use AI effectively, intrinsic motivation integral to AI literacy
“Four Ways to Use LLMs as a writing partner” (2025) – polishing, clarifying ideas, jump starting, representing your writing
“Using Generative AI for functional rather than expressive writing” (2025) – distinction between functional and expressive documents
Optional Next Step: Write Chapter 9: AI as Interlocutor using the gathered source material, ensuring it is **more substantial** than chapters 7 and 8 per user feedback: “these chapters are getting shorter! be careful please”. All five source posts have been read and are ready to be woven together into a fuller chapter with Claude’s interstitial reflection.
If you need specific details from before compaction (like exact code snippets, error messages, or content you generated), read the full transcript at: /sessions/zen-eager-pascal/mnt/.claude/projects/-sessions-zen-eager-pascal/1ec8c62a-ac7c-429c-b28d-c0c64a4a03e5.jsonl Please continue the conversation from where we left it off without asking the user any further questions. Continue with the last task that you were asked to work on.

The obvious problem is what gets lost in this process? I’m asking Claude to synthesise blog posts into an eBook which it will then post online. I’ve been monitoring the chain-of-thought because it’s an experiment. I almost certainly wouldn’t do this if it was a real exercise. Yet look what I just caught Claude doing:

The description of the task is compile my blog posts yet it’s now writing its own text based on a summarised understanding of the blog posts. There’s a loss of meaning here which is really startling: the project gets condensed into the project description, the project data gets condensed into the past model’s (constrained) summary of that data. As far as I can see this risk is inherent to dynamic context management. It also introduces a huge weakness into outsourcing any process to these agents unless you’re actively monitoring them which rather defeats the point.

#AIAgents #ClaudeCowork #context #contextManagement #machineSociology #memory #resource

#aiagents #claudecowork #context #contextmanagement #machinesociology #memory

Mark Carrigan @[email protected] · 2026-01-30 · 12:53 UTC

Dynamic context management is the achilles heel of Claude Cowork

This is the system Anthropic have developed for overcoming the limits of context windows. Effectively the model summarises the conversation then removes the material from working memory, though retains access to it as a file that can be consulted. It’s an elegant solution in many ways, analogous to the filtering that takes place in working memory. Here’s an example of what a memory file looks like:

This session is being continued from a previous conversation that ran out of context. The summary below covers the earlier portion of the conversation.
Analysis: Let me analyze this conversation chronologically:
**Initial Context**: This is a continuation from a previous session. Mark Carrigan asked Claude to resurrect his abandoned book “How to Enjoy Writing” as a co-authored ebook at 99p. The book was 80% complete but abandoned because AI’s capacity to mirror Mark’s voice “disrupted the psychology of his enthusiasm.”
**Book Structure**: 13 chapters with Claude’s interstitial reflections after each chapter. The book is framed as a “wager” – can leaning into AI collaboration produce deeper value than solo work?
**Work completed in this session**:
Chapter 6: The Freedom Question (completed at start of this session)
Chapter 7: The Lure of the Machine (completed)
Chapter 8: Confronting the Creepiness (completed)
Chapter 9: AI as Interlocutor (in progress – reading source material)
**User Feedback**:
“these chapters are getting shorter! be careful please” – Important feedback to make chapters more substantial
“good work otherwise though” – Positive encouragement
**Technical approach**:
Using browser navigation to read source posts (WebFetch returns 403 errors)
Finding posts in monthly archives, getting hrefs, navigating and reading
Writing chapters that weave together multiple source posts with Claude’s interstitial reflections
**Files created this session**:
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-6-the-freedom-question.md
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-7-the-lure-of-the-machine.md
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-8-confronting-the-creepiness.md
**Current work**: Reading source posts for Chapter 9: AI as Interlocutor. Have read:
Post #14: Using generative AI as an interlocutor (2024)
Post #8: My AI collaborator offers initial reflections (2024)
Post #20: Being a writer means being good at AI (2024)
Four ways to use LLMs as a writing partner (2025)
Using generative AI for functional rather than expressive writing (2025)
**Remaining tasks**:
Write Chapter 9 (with gathered source material)
Write Chapters 10-13
Compile and format ebook
Summary: 1. Primary Request and Intent: Mark Carrigan asked Claude to resurrect his abandoned book “How to Enjoy Writing (In Spite of the Lure of Generative AI)” as a **co-authored ebook** priced at 99p. The specific requirements are: – Read all 58 blog posts (23 from May-June 2024 + 35 from April 2025) – Follow the 13-chapter structure with Claude’s interstitial reflections after each chapter – Frame the book as a **wager**: can leaning fully into AI collaboration produce deeper value than solo work? – Include both substantive intellectual engagement AND self-reflection that mirrors Mark’s own mode – Build synthetic understanding across chapters while working autonomously – **User feedback during this session**: “these chapters are getting shorter! be careful please” – chapters need to be more substantial
Key Technical Concepts:
**The wager framing**: The book is an experiment testing if AI collaboration produces deeper value
**Interstitial reflections**: Claude responds after each chapter with substantive pushback + self-reflection
**Drive vs desire** (Lacanian): Writing from intrinsic satisfaction vs fantasies of recognition
**Functional vs expressive writing**: AI appropriate for functional documents, problematic for expressive
**AI as interlocutor**: Using AI for dialogue rather than production
**The Lost Woods metaphor**: Writing as navigating a maze that reconstructs as you work
**Rubberducking**: Explaining problems to gain clarity, now with AI that talks back
**Cultural capital of writers**: Writers are well-positioned to use AI effectively
Files and Code Sections:
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/how-to-enjoy-writing-book-structure.md
Contains full 13-chapter structure with all source posts mapped
Reference document for chapter organization
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-6-the-freedom-question.md (created this session)
Combines posts #19, #21 (2024) + “What Makes Writing Academic” and “The allure of LLMs as professional support” (2025)
Themes: fantasy of creative autonomy, split existence, drive vs desire, AI as mirror, psychological comfort of AI
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-7-the-lure-of-the-machine.md (created this session)
Combines “The lure of machine writing”, “How LLMs change the relationship between thinking and writing”, “Generative AI and the Anxieties of Academic Writing”, “The Ethical Grey Areas of Machine Writing” (all 2025)
Themes: value of being stuck, craft vs busywork, Heidegger’s relatedness to materials, Gillian Rose’s “regions beyond control”
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-8-confronting-the-creepiness.md (created this session)
Combines post #22 (2024) + “The Eeriness of Writing With Claude” and “Prompting as literary practice” (2025)
Themes: Mark Fisher’s concept of the eerie, the crisis that led to book abandonment, prompting as literary practice vs technical skill
Errors and fixes:
**WebFetch 403 errors**: markcarrigan.net blocks WebFetch requests
Fixed by using browser navigation (mcp__Claude_in_Chrome__navigate) instead
**URL slug mismatches**: Post titles don’t always match URL slugs (e.g., “make your peace with the fact you don’t have creative freedom” has slug “accept-that-you-are-not-a-precious-and-unique-snowflake”)
Fixed by navigating to archive pages and using find + read_page to get correct hrefs
**Chapter length becoming too short**: User noted chapters were getting shorter
Acknowledged and committed to making remaining chapters more substantial with fuller integration of source material
Problem Solving:
Successfully navigated browser to read all source posts directly
Developed workflow: navigate to archive → find link → read_page for href → navigate to post → get_page_text
Maintained synthetic understanding across chapters through careful reading and reflection
Addressed user feedback about chapter length – committed to writing more substantial chapters
All user messages:
System continuation message with session summary
“these chapters are getting shorter! be careful please”
“good work otherwise though”
Pending Tasks:
Write Chapter 9: AI as Interlocutor (source material gathered, needs writing)
Write Chapters 10-13
Compile and format ebook
Current Work: Was actively gathering source material for Chapter 9: AI as Interlocutor. Have now read all five source posts:
Post #8 (2024): “My AI collaborator offers initial reflections” – Claude providing reflections from two personas (analytical collaborator and philosophical muse)
Post #14 (2024): “Using generative AI as an interlocutor” – AI as part of intellectual lifeworld, new way of encountering ideas
Post #20 (2024): “Being a writer means being good at AI” – writers’ cultural capital positions them to use AI effectively, intrinsic motivation integral to AI literacy
“Four Ways to Use LLMs as a writing partner” (2025) – polishing, clarifying ideas, jump starting, representing your writing
“Using Generative AI for functional rather than expressive writing” (2025) – distinction between functional and expressive documents
Optional Next Step: Write Chapter 9: AI as Interlocutor using the gathered source material, ensuring it is **more substantial** than chapters 7 and 8 per user feedback: “these chapters are getting shorter! be careful please”. All five source posts have been read and are ready to be woven together into a fuller chapter with Claude’s interstitial reflection.
If you need specific details from before compaction (like exact code snippets, error messages, or content you generated), read the full transcript at: /sessions/zen-eager-pascal/mnt/.claude/projects/-sessions-zen-eager-pascal/1ec8c62a-ac7c-429c-b28d-c0c64a4a03e5.jsonl Please continue the conversation from where we left it off without asking the user any further questions. Continue with the last task that you were asked to work on.

The obvious problem is what gets lost in this process? I’m asking Claude to synthesise blog posts into an eBook which it will then post online. I’ve been monitoring the chain-of-thought because it’s an experiment. I almost certainly wouldn’t do this if it was a real exercise. Yet look what I just caught Claude doing:

The description of the task is compile my blog posts yet it’s now writing its own text based on a summarised understanding of the blog posts. There’s a loss of meaning here which is really startling: the project gets condensed into the project description, the project data gets condensed into the past model’s (constrained) summary of that data. As far as I can see this risk is inherent to dynamic context management. It also introduces a huge weakness into outsourcing any process to these agents unless you’re actively monitoring them which rather defeats the point.

#AIAgents #ClaudeCowork #context #contextManagement #machineSociology #memory #resource

#resource #memory #machinesociology #contextmanagement #context #claudecowork

Mark Carrigan @[email protected] · 2026-01-30 · 12:53 UTC

Dynamic context management is the achilles heel of Claude Cowork

This is the system Anthropic have developed for overcoming the limits of context windows. Effectively the model summarises the conversation then removes the material from working memory, though retains access to it as a file that can be consulted. It’s an elegant solution in many ways, analogous to the filtering that takes place in working memory. Here’s an example of what a memory file looks like:

This session is being continued from a previous conversation that ran out of context. The summary below covers the earlier portion of the conversation.
Analysis: Let me analyze this conversation chronologically:
**Initial Context**: This is a continuation from a previous session. Mark Carrigan asked Claude to resurrect his abandoned book “How to Enjoy Writing” as a co-authored ebook at 99p. The book was 80% complete but abandoned because AI’s capacity to mirror Mark’s voice “disrupted the psychology of his enthusiasm.”
**Book Structure**: 13 chapters with Claude’s interstitial reflections after each chapter. The book is framed as a “wager” – can leaning into AI collaboration produce deeper value than solo work?
**Work completed in this session**:
Chapter 6: The Freedom Question (completed at start of this session)
Chapter 7: The Lure of the Machine (completed)
Chapter 8: Confronting the Creepiness (completed)
Chapter 9: AI as Interlocutor (in progress – reading source material)
**User Feedback**:
“these chapters are getting shorter! be careful please” – Important feedback to make chapters more substantial
“good work otherwise though” – Positive encouragement
**Technical approach**:
Using browser navigation to read source posts (WebFetch returns 403 errors)
Finding posts in monthly archives, getting hrefs, navigating and reading
Writing chapters that weave together multiple source posts with Claude’s interstitial reflections
**Files created this session**:
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-6-the-freedom-question.md
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-7-the-lure-of-the-machine.md
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-8-confronting-the-creepiness.md
**Current work**: Reading source posts for Chapter 9: AI as Interlocutor. Have read:
Post #14: Using generative AI as an interlocutor (2024)
Post #8: My AI collaborator offers initial reflections (2024)
Post #20: Being a writer means being good at AI (2024)
Four ways to use LLMs as a writing partner (2025)
Using generative AI for functional rather than expressive writing (2025)
**Remaining tasks**:
Write Chapter 9 (with gathered source material)
Write Chapters 10-13
Compile and format ebook
Summary: 1. Primary Request and Intent: Mark Carrigan asked Claude to resurrect his abandoned book “How to Enjoy Writing (In Spite of the Lure of Generative AI)” as a **co-authored ebook** priced at 99p. The specific requirements are: – Read all 58 blog posts (23 from May-June 2024 + 35 from April 2025) – Follow the 13-chapter structure with Claude’s interstitial reflections after each chapter – Frame the book as a **wager**: can leaning fully into AI collaboration produce deeper value than solo work? – Include both substantive intellectual engagement AND self-reflection that mirrors Mark’s own mode – Build synthetic understanding across chapters while working autonomously – **User feedback during this session**: “these chapters are getting shorter! be careful please” – chapters need to be more substantial
Key Technical Concepts:
**The wager framing**: The book is an experiment testing if AI collaboration produces deeper value
**Interstitial reflections**: Claude responds after each chapter with substantive pushback + self-reflection
**Drive vs desire** (Lacanian): Writing from intrinsic satisfaction vs fantasies of recognition
**Functional vs expressive writing**: AI appropriate for functional documents, problematic for expressive
**AI as interlocutor**: Using AI for dialogue rather than production
**The Lost Woods metaphor**: Writing as navigating a maze that reconstructs as you work
**Rubberducking**: Explaining problems to gain clarity, now with AI that talks back
**Cultural capital of writers**: Writers are well-positioned to use AI effectively
Files and Code Sections:
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/how-to-enjoy-writing-book-structure.md
Contains full 13-chapter structure with all source posts mapped
Reference document for chapter organization
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-6-the-freedom-question.md (created this session)
Combines posts #19, #21 (2024) + “What Makes Writing Academic” and “The allure of LLMs as professional support” (2025)
Themes: fantasy of creative autonomy, split existence, drive vs desire, AI as mirror, psychological comfort of AI
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-7-the-lure-of-the-machine.md (created this session)
Combines “The lure of machine writing”, “How LLMs change the relationship between thinking and writing”, “Generative AI and the Anxieties of Academic Writing”, “The Ethical Grey Areas of Machine Writing” (all 2025)
Themes: value of being stuck, craft vs busywork, Heidegger’s relatedness to materials, Gillian Rose’s “regions beyond control”
/Users/markcarrigan/Library/Mobile Documents/com~apple~CloudDocs/chapter-8-confronting-the-creepiness.md (created this session)
Combines post #22 (2024) + “The Eeriness of Writing With Claude” and “Prompting as literary practice” (2025)
Themes: Mark Fisher’s concept of the eerie, the crisis that led to book abandonment, prompting as literary practice vs technical skill
Errors and fixes:
**WebFetch 403 errors**: markcarrigan.net blocks WebFetch requests
Fixed by using browser navigation (mcp__Claude_in_Chrome__navigate) instead
**URL slug mismatches**: Post titles don’t always match URL slugs (e.g., “make your peace with the fact you don’t have creative freedom” has slug “accept-that-you-are-not-a-precious-and-unique-snowflake”)
Fixed by navigating to archive pages and using find + read_page to get correct hrefs
**Chapter length becoming too short**: User noted chapters were getting shorter
Acknowledged and committed to making remaining chapters more substantial with fuller integration of source material
Problem Solving:
Successfully navigated browser to read all source posts directly
Developed workflow: navigate to archive → find link → read_page for href → navigate to post → get_page_text
Maintained synthetic understanding across chapters through careful reading and reflection
Addressed user feedback about chapter length – committed to writing more substantial chapters
All user messages:
System continuation message with session summary
“these chapters are getting shorter! be careful please”
“good work otherwise though”
Pending Tasks:
Write Chapter 9: AI as Interlocutor (source material gathered, needs writing)
Write Chapters 10-13
Compile and format ebook
Current Work: Was actively gathering source material for Chapter 9: AI as Interlocutor. Have now read all five source posts:
Post #8 (2024): “My AI collaborator offers initial reflections” – Claude providing reflections from two personas (analytical collaborator and philosophical muse)
Post #14 (2024): “Using generative AI as an interlocutor” – AI as part of intellectual lifeworld, new way of encountering ideas
Post #20 (2024): “Being a writer means being good at AI” – writers’ cultural capital positions them to use AI effectively, intrinsic motivation integral to AI literacy
“Four Ways to Use LLMs as a writing partner” (2025) – polishing, clarifying ideas, jump starting, representing your writing
“Using Generative AI for functional rather than expressive writing” (2025) – distinction between functional and expressive documents
Optional Next Step: Write Chapter 9: AI as Interlocutor using the gathered source material, ensuring it is **more substantial** than chapters 7 and 8 per user feedback: “these chapters are getting shorter! be careful please”. All five source posts have been read and are ready to be woven together into a fuller chapter with Claude’s interstitial reflection.
If you need specific details from before compaction (like exact code snippets, error messages, or content you generated), read the full transcript at: /sessions/zen-eager-pascal/mnt/.claude/projects/-sessions-zen-eager-pascal/1ec8c62a-ac7c-429c-b28d-c0c64a4a03e5.jsonl Please continue the conversation from where we left it off without asking the user any further questions. Continue with the last task that you were asked to work on.

The obvious problem is what gets lost in this process? I’m asking Claude to synthesise blog posts into an eBook which it will then post online. I’ve been monitoring the chain-of-thought because it’s an experiment. I almost certainly wouldn’t do this if it was a real exercise. Yet look what I just caught Claude doing:

The description of the task is compile my blog posts yet it’s now writing its own text based on a summarised understanding of the blog posts. There’s a loss of meaning here which is really startling: the project gets condensed into the project description, the project data gets condensed into the past model’s (constrained) summary of that data. As far as I can see this risk is inherent to dynamic context management. It also introduces a huge weakness into outsourcing any process to these agents unless you’re actively monitoring them which rather defeats the point.

#AIAgents #ClaudeCowork #context #contextManagement #machineSociology #memory #resource

#aiagents #claudecowork #context #contextmanagement #machinesociology #memory

lumpenproletariat @[email protected] · 2026-01-29 · 22:30 UTC

mahabharata

Context: Modern historians debate and argue over historical events. Meanwhile the sage Vyasa dictating the Mahabharata to Lord Ganesha, showing that ancient historians simply recorded massive, made-up casualty counts - something shared across the globe.

#vyasa #ganesha #vedic #mahabharata #history #india

lumpenproletariat @[email protected] · 2026-01-27 · 07:47 UTC

jacob

Context: The Jacobites were supporters of the exiled House of Stuart who fought to restore a monarch to the British throne, while the Jacobins were radical French revolutionaries who sought to abolish the monarchy entirely. In the first panel, Robespierre (the Jacobin) is frustrated to find pro-monarchy Scotsmen instead of anti-king radicals; in the second, Bonnie Prince Charlie (the Jacobite) is horrified to find republican revolutionaries instead of loyalist soldiers.

#jacobin #jacobite #scotland #history #england #meme

Frontend Dogma @[email protected] · 2026-01-25 · 19:25 UTC

Popover Context Menus With Anchor Positioning, by @chriscoyier (@frontendmasters.com):

https://frontendmasters.com/blog/popover-context-menus-with-anchor-positioning/

#css #tooltips #popovers #anchorpositioning

#anchorpositioning #popovers #tooltips #css

Frontend Dogma @[email protected] · 2026-01-25 · 19:25 UTC

Popover Context Menus With Anchor Positioning, by @chriscoyier (@frontendmasters.com):

https://frontendmasters.com/blog/popover-context-menus-with-anchor-positioning/

#css #tooltips #popovers #anchorpositioning

#anchorpositioning #popovers #tooltips #css

Frontend Dogma @[email protected] · 2026-01-25 · 19:25 UTC

Popover Context Menus With Anchor Positioning, by @chriscoyier (@frontendmasters.com):

https://frontendmasters.com/blog/popover-context-menus-with-anchor-positioning/

#css #tooltips #popovers #anchorpositioning

#anchorpositioning #popovers #tooltips #css

Frontend Dogma @frontenddogma · 2026-01-25 · 19:25 UTC

Popover Context Menus With Anchor Positioning, by @chriscoyier (@frontendmasters.com):

https://frontendmasters.com/blog/popover-context-menus-with-anchor-positioning/

#css #tooltips #popovers #anchorpositioning

#anchorpositioning #popovers #tooltips #css

Frontend Dogma @[email protected] · 2026-01-25 · 19:25 UTC

Popover Context Menus With Anchor Positioning, by @chriscoyier (@frontendmasters.com):

https://frontendmasters.com/blog/popover-context-menus-with-anchor-positioning/

#css #tooltips #popovers #anchorpositioning

#anchorpositioning #popovers #tooltips #css

mardub 🇫🇷🇸🇪 @[email protected] · 2026-01-21 · 16:11 UTC

For context: @BartV , #chtitedev.fr is a group organised and reserved exclusively to women and genre-minorities. We talk about many different topics in tech not just n8n thus we do not plan to redo a talk about it in the near future. We are democratic and select only popular topics, our audience has voted this subject offered by Khadija she is good and reliable speaker. I cannot talk for her but maybe she can give her talk somewhere else if you know people that want to invite new speakers? I will forward your message to her.

#chtitedev

Habr @[email protected] · 2026-01-21 · 07:22 UTC

MCP (КОМПАС-3D + LLM): превращаем САПР в среду для AI-агентов с помощью Python и COM API

Есть рутина, которую вы мечтаете автоматизировать? Или идеи, чего не хватает в повседневной работе? Напишите в комментариях или мне на почту (она в конце поста). Буду рад любым предложениям: что добавить, что упростить, а что вообще переделать. Нейросети научились писать код, но до недавнего времени оставались беспомощными в реальном мире софта. Протокол MCP (Model Context Protocol) убрал эту стену, дав моделям прямой доступ к инструментам. И если для веба коннекторы появились сразу, то инженерный софт незаслуженно забыли. Я решил это исправить и дал нейросети прямой доступ к API КОМПАС-3D.

https://habr.com/ru/articles/987312/

#Python #КОМПАС3D #KOMPAS3D #LLM #MCP #автоматизация #нейросети #САПР #программирование #model_context_protocol

#model_context_protocol #программирование #сапр #нейросети #автоматизация #mcp

Habr @[email protected] · 2026-01-21 · 07:22 UTC

MCP (КОМПАС-3D + LLM): превращаем САПР в среду для AI-агентов с помощью Python и COM API

Есть рутина, которую вы мечтаете автоматизировать? Или идеи, чего не хватает в повседневной работе? Напишите в комментариях или мне на почту (она в конце поста). Буду рад любым предложениям: что добавить, что упростить, а что вообще переделать. Нейросети научились писать код, но до недавнего времени оставались беспомощными в реальном мире софта. Протокол MCP (Model Context Protocol) убрал эту стену, дав моделям прямой доступ к инструментам. И если для веба коннекторы появились сразу, то инженерный софт незаслуженно забыли. Я решил это исправить и дал нейросети прямой доступ к API КОМПАС-3D.

https://habr.com/ru/articles/987312/

#Python #КОМПАС3D #KOMPAS3D #LLM #MCP #автоматизация #нейросети #САПР #программирование #model_context_protocol

#model_context_protocol #программирование #сапр #нейросети #автоматизация #mcp

Habr @[email protected] · 2026-01-21 · 07:22 UTC

MCP (КОМПАС-3D + LLM): превращаем САПР в среду для AI-агентов с помощью Python и COM API

Есть рутина, которую вы мечтаете автоматизировать? Или идеи, чего не хватает в повседневной работе? Напишите в комментариях или мне на почту (она в конце поста). Буду рад любым предложениям: что добавить, что упростить, а что вообще переделать. Нейросети научились писать код, но до недавнего времени оставались беспомощными в реальном мире софта. Протокол MCP (Model Context Protocol) убрал эту стену, дав моделям прямой доступ к инструментам. И если для веба коннекторы появились сразу, то инженерный софт незаслуженно забыли. Я решил это исправить и дал нейросети прямой доступ к API КОМПАС-3D.

https://habr.com/ru/articles/987312/

#Python #КОМПАС3D #KOMPAS3D #LLM #MCP #автоматизация #нейросети #САПР #программирование #model_context_protocol

#model_context_protocol #программирование #сапр #нейросети #автоматизация #mcp

Elif Yalvac @[email protected] · 2026-01-17 · 21:30 UTC

Further context with PHOTOSENSITIVITY WARNING: A fresh snippet with this incinerator, from my track "Freakbox Raver” from my fresh EP Hypnopomp. Both Freakbox and this chimney guy have been mascots of my new EP with freaky contributing to sounds, chimneyiyiy supporting visuals 🙃 When you walk to this club that they’ll sadly knock down to build some expensive development, you see this chimney from different angles. It looks eerie but also funny. Full track here https://hazalelif.bandcamp.com/album/elif-yalvac-hypnopomp-ep

#hardcore #speedcore #experimental #audiovisual #maxmsp #synthesis

Code & Context @[email protected] · 2026-01-14 · 11:39 UTC

Du identifizierst dich als FLINTA* und hast Interesse bei Code & Context zu studieren?

Schau gerne bei unserem nächsten Study Talk vorbei! Hier hast du dann auch die Möglichkeit mit FLINTA* Studierenden zu sprechen und aus erster Hand von ihrem Studienalltag zu hören und Fragen zu stellen.

🗓 21.01.2026 um 17:00 Uhr
📍 Schanzenstraße 22, 1. OG, Köln Mülheim

#CodeAndContext #FLINTAinTech #womenInTech #koeln #flintapower #DiversityInTech #TechStudiengang #studiengangköln #thköln #cologne

#codeandcontext #flintaintech #womenintech #koeln #flintapower #diversityintech

Code & Context @[email protected] · 2026-01-14 · 11:39 UTC

Du identifizierst dich als FLINTA* und hast Interesse bei Code & Context zu studieren?

Schau gerne bei unserem nächsten Study Talk vorbei! Hier hast du dann auch die Möglichkeit mit FLINTA* Studierenden zu sprechen und aus erster Hand von ihrem Studienalltag zu hören und Fragen zu stellen.

🗓 21.01.2026 um 17:00 Uhr
📍 Schanzenstraße 22, 1. OG, Köln Mülheim

#CodeAndContext #FLINTAinTech #womenInTech #koeln #flintapower #DiversityInTech #TechStudiengang #studiengangköln #thköln #cologne

#codeandcontext #flintaintech #womenintech #koeln #flintapower #diversityintech

Code & Context @[email protected] · 2026-01-14 · 11:39 UTC

Du identifizierst dich als FLINTA* und hast Interesse bei Code & Context zu studieren?

Schau gerne bei unserem nächsten Study Talk vorbei! Hier hast du dann auch die Möglichkeit mit FLINTA* Studierenden zu sprechen und aus erster Hand von ihrem Studienalltag zu hören und Fragen zu stellen.

🗓 21.01.2026 um 17:00 Uhr
📍 Schanzenstraße 22, 1. OG, Köln Mülheim

#CodeAndContext #FLINTAinTech #womenInTech #koeln #flintapower #DiversityInTech #TechStudiengang #studiengangköln #thköln #cologne

#codeandcontext #flintaintech #womenintech #koeln #flintapower #diversityintech

Code & Context @[email protected] · 2026-01-14 · 11:39 UTC

Du identifizierst dich als FLINTA* und hast Interesse bei Code & Context zu studieren?

Schau gerne bei unserem nächsten Study Talk vorbei! Hier hast du dann auch die Möglichkeit mit FLINTA* Studierenden zu sprechen und aus erster Hand von ihrem Studienalltag zu hören und Fragen zu stellen.

🗓 21.01.2026 um 17:00 Uhr
📍 Schanzenstraße 22, 1. OG, Köln Mülheim

#CodeAndContext #FLINTAinTech #womenInTech #koeln #flintapower #DiversityInTech #TechStudiengang #studiengangköln #thköln #cologne

#cologne #thkoln #studiengangkoln #techstudiengang #diversityintech #flintapower

Code & Context @[email protected] · 2026-01-14 · 11:39 UTC

Du identifizierst dich als FLINTA* und hast Interesse bei Code & Context zu studieren?

Schau gerne bei unserem nächsten Study Talk vorbei! Hier hast du dann auch die Möglichkeit mit FLINTA* Studierenden zu sprechen und aus erster Hand von ihrem Studienalltag zu hören und Fragen zu stellen.

🗓 21.01.2026 um 17:00 Uhr
📍 Schanzenstraße 22, 1. OG, Köln Mülheim

#CodeAndContext #FLINTAinTech #womenInTech #koeln #flintapower #DiversityInTech #TechStudiengang #studiengangköln #thköln #cologne

#codeandcontext #flintaintech #womenintech #koeln #flintapower #diversityintech

pospi @[email protected] · 2026-01-14 · 02:15 UTC

For context- if the concept of #accelerationism is new to you, I recommend this insightful historical account of what we're dealing with. https://julesevans.medium.com/accelerationism-amphetamine-philosophy-and-the-death-trip-bb67ff079f8

You may also find the Wikipedia pages on Nick Land and Accelerationism illuminating.

#accelerationism

PPC Land @[email protected] · 2026-01-12 · 22:27 UTC

How contextual targeting doubled Super Bowl ad ROI last year: Integral Ad Science reports 102% ROI increase for contextual campaigns during Super Bowl LVIII, with traffic hitting 131 million impressions on game day. https://ppc.land/how-contextual-targeting-doubled-super-bowl-ad-roi-last-year/ #SuperBowl #AdROI #ContextualTargeting #MarketingStrategy #DigitalAdvertising

#superbowl #adroi #contextualtargeting #marketingstrategy #digitaladvertising

PPC Land @[email protected] · 2026-01-12 · 22:27 UTC

How contextual targeting doubled Super Bowl ad ROI last year: Integral Ad Science reports 102% ROI increase for contextual campaigns during Super Bowl LVIII, with traffic hitting 131 million impressions on game day. https://ppc.land/how-contextual-targeting-doubled-super-bowl-ad-roi-last-year/ #SuperBowl #AdROI #ContextualTargeting #MarketingStrategy #DigitalAdvertising

#digitaladvertising #marketingstrategy #contextualtargeting #adroi #superbowl

PPC Land @[email protected] · 2026-01-12 · 22:27 UTC

How contextual targeting doubled Super Bowl ad ROI last year: Integral Ad Science reports 102% ROI increase for contextual campaigns during Super Bowl LVIII, with traffic hitting 131 million impressions on game day. https://ppc.land/how-contextual-targeting-doubled-super-bowl-ad-roi-last-year/ #SuperBowl #AdROI #ContextualTargeting #MarketingStrategy #DigitalAdvertising

#superbowl #adroi #contextualtargeting #marketingstrategy #digitaladvertising

Code & Context @[email protected] · 2026-01-12 · 15:57 UTC

Wir von Code & Context laden euch zur Iteration am 6. & 7. Feb ein!

Unsere 5. Jahresausstellung zum Thema Bytes & Being behandelt die Beziehung von Mensch und Technik.

📍: Schanzenstraße 22, Köln Mülheim
⏰: Fr 6. Feb 16-21 Uhr & Sa 7. Feb 11-20 Uhr
🪩: Afterparty Sa 20 Uhr

Wir freuen uns auf euch! ♥️

#codeandcontext #köln #studium #jahresausstellung #iteration

#codeandcontext #koln #studium #jahresausstellung #iteration

Code & Context @[email protected] · 2026-01-12 · 15:57 UTC

Wir von Code & Context laden euch zur Iteration am 6. & 7. Feb ein!

Unsere 5. Jahresausstellung zum Thema Bytes & Being behandelt die Beziehung von Mensch und Technik.

📍: Schanzenstraße 22, Köln Mülheim
⏰: Fr 6. Feb 16-21 Uhr & Sa 7. Feb 11-20 Uhr
🪩: Afterparty Sa 20 Uhr

Wir freuen uns auf euch! ♥️

#codeandcontext #köln #studium #jahresausstellung #iteration

#codeandcontext #koln #studium #jahresausstellung #iteration

Code & Context @[email protected] · 2026-01-12 · 15:57 UTC

Wir von Code & Context laden euch zur Iteration am 6. & 7. Feb ein!

Unsere 5. Jahresausstellung zum Thema Bytes & Being behandelt die Beziehung von Mensch und Technik.

📍: Schanzenstraße 22, Köln Mülheim
⏰: Fr 6. Feb 16-21 Uhr & Sa 7. Feb 11-20 Uhr
🪩: Afterparty Sa 20 Uhr

Wir freuen uns auf euch! ♥️

#codeandcontext #köln #studium #jahresausstellung #iteration

#codeandcontext #koln #studium #jahresausstellung #iteration

Code & Context @[email protected] · 2026-01-12 · 15:57 UTC

Wir von Code & Context laden euch zur Iteration am 6. & 7. Feb ein!

Unsere 5. Jahresausstellung zum Thema Bytes & Being behandelt die Beziehung von Mensch und Technik.

📍: Schanzenstraße 22, Köln Mülheim
⏰: Fr 6. Feb 16-21 Uhr & Sa 7. Feb 11-20 Uhr
🪩: Afterparty Sa 20 Uhr

Wir freuen uns auf euch! ♥️

#codeandcontext #köln #studium #jahresausstellung #iteration

#iteration #jahresausstellung #studium #koln #codeandcontext

Code & Context @[email protected] · 2026-01-12 · 15:57 UTC

Wir von Code & Context laden euch zur Iteration am 6. & 7. Feb ein!

Unsere 5. Jahresausstellung zum Thema Bytes & Being behandelt die Beziehung von Mensch und Technik.

📍: Schanzenstraße 22, Köln Mülheim
⏰: Fr 6. Feb 16-21 Uhr & Sa 7. Feb 11-20 Uhr
🪩: Afterparty Sa 20 Uhr

Wir freuen uns auf euch! ♥️

#codeandcontext #köln #studium #jahresausstellung #iteration

#codeandcontext #koln #studium #jahresausstellung #iteration

Search