AI Engineer Europe 2026
Cognitive Exhaust Fumes, or: Read-Only AI Is Underrated — Šimon Podhajský, Head of AI, Waypoint
Loading slides…
Read the talk
Cognitive Exhaust Fumes, or: Read-Only AI Is Underrated
A personal AI can connect your reading, commitments, and relationships without acting for you. The useful boundary separates observation from action, but it does not eliminate privacy risk.
From a talk by Šimon Podhajský
What can an AI learn without acting for you?
What would a personal AI be useful for if it knew you but could not send a message, change a task, or act on your behalf? Šimon Podhajský starts with that constraint: six data sources, read access only, and no permissions to write back. The restriction is intentional, not an unfinished step toward automation.
He calls the raw material cognitive exhaust fumes: digital activity left behind as a byproduct of thinking. A single trace may look disposable. Taken together, those traces can reveal patterns in the activity that produced them, much as analyzing exhaust can help diagnose an engine.
The useful patterns cross application boundaries:
- Intention-action gaps: differences between what you intend to do and what your activity shows.
- Attention drift: changes in what captures your attention.
- Relationship decay: connections that receive less attention over time.
Your email client does not know what you journaled; your task manager does not know what you browsed. The cross-source signal is the product.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Separate sources, analysis, and outputs
Read-only does not mean the system cannot create a file. It means the AI cannot modify the sources it observes. Podhajský separates the system into three zones:
| Zone | Purpose | Write boundary |
|---|---|---|
| Sources | Supply personal activity | No AI writes back |
| Workspace | Analyze the collected material | Analysis happens here |
| Outputs | Hold results for human review | Separate from the sources |
His outputs land in a separate Obsidian vault. A separate Notion destination or ordinary text files would serve the same purpose: analysis becomes something to review without rewriting the underlying record.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Turn a week of activity into reflection
The first application is a weekly reflection inspired by David Allen’s Getting Things Done Weekly Review. Instead of asking the user to reconstruct the week from memory, the system synthesizes material from all six sources. The result can be an occasionally brutal account of how the week was spent.
The workflow runs through Claude, with the logic packaged as a slash command or skill:
- Invoke the weekly reflection skill.
- Launch a Python script that gathers data from the read-only sources.
- Apply prepared prompts and call the Anthropic API for structured outputs.
- Turn those outputs into a Markdown document for review.
The separation between structured analysis and document rendering makes the final artifact straightforward to inspect. A small Python renderer illustrates that last step, taking already-produced analysis and writing only to a separate output directory:
python
from pathlib import Path
def write_reflection(sections: dict[str, list[str]], output_dir: Path) -> Path:
output_dir.mkdir(parents=True, exist_ok=True)
document = ["# Weekly reflection"]
for heading, items in sections.items():
document.append(f"## {heading}")
document.append("\n".join(f"- {item}" for item in items))
destination = output_dir / "weekly-reflection.md"
destination.write_text("\n\n".join(document) + "\n", encoding="utf-8")
return destination
This output convention expresses the architecture; source permissions must enforce the read-only boundary separately.
When the run finishes, Podhajský opens the Markdown in Cursor and switches to a readable preview. It identifies themes of the week, tensions and conflicts, commitments and relationships, notable moments, and questions for reflection. The relationship and commitment sections are revealing partly through omissions: what did not receive attention can matter as much as what did. The aim is to reflect on how he is thinking, rather than produce a productivity score.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Find someone to discuss your reading with
The next question is more specific: given what I have been reading, who in my network should I discuss it with? Podhajský enjoys sharing reading with others but wants to look beyond the same three habitual recipients. This example combines four sources that were not designed to work together. Its output is a suggestion: nothing is sent and nothing is scheduled.
A plain-language request activates the cross-source query skill. It works through curated databases that receive regular ingestion, including a Vivaldi SQLite database used to examine reading activity. The query identifies articles he has read frequently and articles still open in tabs, then looks for people whose profiles suggest an interest in those topics.
Clay MCP supplies the relationship search. Podhajský describes Clay as his CRM—or, more personally, his friend relationship system. In this run, Claude searches for contacts interested in AI, European tech, and education. He calls this the weakest part of the workflow because the Clay searches are slow. The read-only constraint belongs to his system’s configuration; it should not be inferred merely from the connector’s name.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
From large search responses to specific recommendations
The search results consume substantial context. Podhajský recommends starting with a clean session and clearing it afterward; he refers to a one-million-token context window for “4.6.” That is a capacity reference, not measured token usage or retrieval accuracy. Both Claude Opus 4.6 and Claude Sonnet 4.6 were announced with that capacity, so the shorthand does not identify the demo’s exact variant or enabled limit.
Once the Clay responses arrive, Claude synthesizes the candidate contacts and maps each person to one article. As the demonstration continues, that mapping is still being assembled with shell commands in Claude Code. Podhajský mentions auto mode and --dangerously-skip-permissions as ways to reduce permission friction. They have different protections: auto mode makes permission decisions with safeguards, while the flag bypasses permission checks. Neither establishes the source-access boundary.
The finished recommendations look useful to him: people he might want to approach, whom he has not yet talked to about these readings. The result even finds an article’s author already in his network. In the displayed table, Jiří Dolejš appears with the rationale “He wrote it,” alongside contact, rationale, and opener columns. The proposed conversation remains for Podhajský to initiate.
The browser alone could identify reading activity but would lack the contacts. The CRM could find people but would lack the reading context. Joining those records produces a person-to-article recommendation that neither source can supply on its own.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Keep action—and the feedback loop—with the user
Why stop at a recommendation when the system could send the message? Podhajský’s answer begins with asymmetric consequences. He calls the downside of an incorrect read-only suggestion zero when he can simply ignore it. An incorrect write can instead affect a relationship, a career, or a reputation. That comparison concerns the consequences of acting on someone’s behalf; it does not establish that reading private data is risk-free. He would rather forgo automated emails than accept a consequential misfire.
The second reason concerns the quality of the evidence. If AI starts writing into the same systems it analyzes, future observations mix human activity with AI-generated activity. A pattern in the record becomes harder to attribute: is this how the person thinks, or how the automation behaves? Keeping sources untouched preserves a clearer record of the activity being observed.
An observer still changes behavior. Reading a reflection may prompt a different decision next week. But the loop runs through the person: read, decide, then act. It does not automatically close through an AI rewrite. Podhajský extends this into a preference for reclaiming personal agency, even in drafting—while acknowledging that this preference may be a hard sell to an audience building AI tools.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
An observer serves a different need
Podhajský has also tried OpenClaw with a read-only mount. His preference for a dedicated observer comes from the value he experiences per interaction. His illustrative comparison is an agent saving thirty seconds on a weather check versus an observer revealing two weeks of avoiding his most important project. This is his assessment of usefulness, not a measured comparison between products.
He also sees less opportunity for exfiltration and less contamination of the observed record, although the security boundary needs closer examination. The product distinction stands independently: agents perform actions; observers help people notice and interpret patterns. Read-only need not be a capability users eventually graduate from. As he puts it, “A mirror isn't a broken butler.”
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
The useful combination is also a sensitive target
The same cross-referencing that makes the observer valuable creates its central privacy risk. The mosaic effect is what happens when many small pieces of information combine into a revealing picture. A fragment that seems modest in isolation may become sensitive when connected to other fragments. Podhajský’s own product description therefore doubles as a threat description: the combined view is an attractive target precisely because it reveals more than any single source. Read-only access protects the source record from modification; it does not make that combined picture confidential.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Read-only does not close the exfiltration path
Simon Willison’s lethal trifecta makes the remaining risk explicit: private data, untrusted content, and external communication coexist in one system. Podhajský initially thought read-only access broke that combination. He then recognized that removing source writes only removes some natural exfiltration channels. Shell access can still communicate externally, so the third capability remains.
Even in ordinary operation, this system sends data to Anthropic. Podhajský describes a mostly open network and more accessible information than the task strictly requires. He does not claim the system is secure or fireproof. His position is that he has examined its exposure and decided which risks he is willing to carry—a different posture from leaving them unrecognized.
That leaves a useful, bounded purpose for the system: turn an underused personal dataset into material for reflection. Your digital activity already records traces of attention, commitments, and relationships. Bringing those traces together can help you decide what to change, while leaving the decision and the action with you.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Resources
From the talk
Explains how private data, untrusted inputs, and external communication combine to enable data theft through prompt injection.
Explains automated permission decisions and how they differ from disabling permission checks.
David Allen's discussion of the Weekly Review, with eleven review steps and a checklist.
Further reading
The February 2026 announcement introducing Opus 4.6 and its one-million-token context window in beta.
Updates since the talk
Current documentation for extending Claude Code with reusable skills.
Current sandbox configuration guidance, including read-only workspace access and separate mount permissions.
Full transcript
Loading transcript…