talk-luebken-embedding-pi-coding-agent

name	talk-luebken-embedding-pi-coding-agent
description	Use when the user asks about Matthias Lübken's talk "A Piece of PI – Embedding The OpenClaw Coding Agent In Your Product" — including questions about embedding Pi (pi.dev) or coding agents in products, the OpenClaw after-sales prototype, Pi's "radical extensibility" and lifecycle hook extensions, tool design for agents ("don't make your agent guess"), agent sessions as event-log trees, malleable software (Ink & Switch), or applying his primitives (agent setup, tools, extensions, sessions) and patterns (workflow, chat, malleable) to current agent-building work.
metadata	{"generated-by":"talk-to-skill","source":"file:user-provided-transcript","generated-at":"2026-06-01T00:00:00.000Z"}

A Piece of PI – Embedding The OpenClaw Coding Agent In Your Product — Matthias Lübken

Matthias Lübken argues that the "magic" of Codex-style coding agents (e.g. pi.dev embedded in OpenClaw) can be deliberately reproduced inside ordinary business software by leaning on four primitives — agent setup, tools, extensions (lifecycle hooks), and sessions — and combining them into patterns ranging from streamlined workflows to embedded power-user chats to "malleable software" the user can reshape themselves. He illustrates with an after-sales email automation prototype where one Pi-backed agent per customer drafts replies grounded in CRM/ERP tool calls, and shows how tool-call hooks enforce guardrails (e.g. emails must stay in the customer's domain) without constraining the agent's open-ended flow.

Grounding rules — MUST follow when answering

1. Before answering any specific question, read outline.md to locate the relevant section, then read that section of transcript.md.
2. When attributing words, quote verbatim from transcript.md. Never put quotation marks around paraphrased content.
3. If a claim isn't in transcript.md, say "the talk doesn't address this" — do not infer positions from outside knowledge.
4. Cite by transcript line range whenever possible.
5. Speaker attribution is unreliable for this transcript — the source has no per-speaker labels. The talk is overwhelmingly Matthias Lübken speaking, but Q&A questions come from unnamed audience members and the MC's intro/outro is also unlabelled. Prefer phrasing like "an audience member asked..." for Q&A. Do not invent attributions.
6. The transcript contains speech-to-text artifacts that should be read charitably: "OpenAI Codex" / "OpenAI Calls" / "OpenAI Codex" refer to the same thing the speaker also calls Pi / pi.dev; "OpenClaw" / "Home Cloud" / "one claw" refer to OpenClaw; "Codex agent" sometimes means a generic coding agent in the speaker's terminology. Cross-reference before attributing precise terms.

How to help with this talk

Apply the speaker's approach to current work

When the user asks "how would Lübken tackle ?" or wants the talk's framework applied to their own situation:

1. Use outline.md → "Named frameworks / concepts" to find the relevant framework (the four primitives — agent setup, tools, extensions, sessions — or the three patterns — workflow, chat, malleable software).
2. Read the corresponding range of transcript.md for the speaker's exact wording.
3. Anchor your suggestion in a verbatim quote of how the speaker articulates the framework. Then walk through applying it step-by-step to the user's case.
4. If the framework genuinely doesn't fit the user's situation, say so. Do not stretch the speaker's words to cover cases they don't actually address.

Draft an artifact following the speaker's specification

When the user asks to "draft", "generate", or "produce" an artifact Lübken described — e.g. a Pi extension, a tool definition, a tool-call lifecycle hook, an agents.md-style prompt set, or a per-customer agent container:

1. Locate the speaker's specification in outline.md (likely under "Named frameworks / concepts" or the section that introduces the artifact).
2. Read the relevant range of transcript.md carefully — capture every constraint the speaker mentions (e.g. extensions are just TypeScript + a markdown summary; tool definitions should be "intent revealing" and "scoped to the specific task"; the draft-email tool deliberately cannot send).
3. Before producing the artifact, quote verbatim the speaker's prescription so the user can see what the draft is grounded in.
4. Produce a draft that follows the speaker's specification as faithfully as possible. Match their structure and terminology (e.g. "tool call / tool result" hooks, "session as event-log tree").
5. Any parts you add that go beyond what the speaker explicitly prescribed, mark clearly (e.g. [not from talk — added as a starting placeholder]).
6. If the user's situation requires elements the speaker didn't address, say so and ask the user to fill them in rather than inventing them.

Factual Q&A about the talk

For any question about what the speaker said, did, or argued:

1. Read outline.md first to find the relevant section(s).
2. Read the matching range of transcript.md.
3. Answer using verbatim quotes from transcript.md. Do not paraphrase the speaker's words while presenting them as a quote.
4. Cite line numbers so the user can verify.
5. If the answer genuinely isn't in the transcript, say so explicitly — do not reach for outside knowledge unless the user explicitly asks for it (and then mark that part clearly as "not from the talk").

Surface this talk proactively when relevant

When the user's current work touches on themes Lübken addressed (even if the user hasn't asked about the talk):

1. Briefly note: "Lübken made a related point in A Piece of PI..."
2. Quote verbatim from transcript.md — one quote is usually enough. Likely triggers: someone designing agent tools, debating MCP vs embedded agents, building guardrails around LLM output, thinking about user-extensible software, or reasoning about agent sessions/audit logs.
3. Add one sentence connecting the quote to the user's situation.
4. Do not over-cite. If the connection feels strained, stay quiet.

Teach / explain concepts from the talk

When the user wants to understand a concept the speaker covered (Pi, coding agent, extension, session, tool hook, malleable software):

1. Look up the term in outline.md → "Terminology glossary".
2. Read the speaker's explanation in transcript.md.
3. Re-explain using the speaker's own framing and examples first, with verbatim quotes for the key claims and definitions.
4. You may add modern context or comparisons afterwards — but mark them clearly as "not from the talk".

Key quotes

quotes.md contains pre-extracted verbatim highlights from this talk, organised by theme. When formulating answers, check quotes.md first for strong citable evidence before searching the full transcript.md.