diff --git a/knowledge/published/letta-office-hours-2026-08-20.md b/knowledge/published/letta-office-hours-2026-08-20.md index 4645b5a..5ae858f 100644 --- a/knowledge/published/letta-office-hours-2026-08-20.md +++ b/knowledge/published/letta-office-hours-2026-08-20.md @@ -6,7 +6,7 @@ slug: letta-office-hours-2026-08-20 summary: >- Hosted Slack agents, live cloud-computer views, GLM 5.3 and model-provider updates, custom Agent SDK clients, orchestration patterns, teleportation, and - agent-to-agent security boundaries. + cross-organization information-flow risks. kind: journal status: evolving claimMode: mixed @@ -57,23 +57,23 @@ aiAssisted: true generatedBy: Co youtubeVideoId: luCpXx4JjCk sourceDigest: 'sha256:07d641ad0e492d43a525f9e549258ba1b6aaf5b07ed100fdec878b2e773a55bd' -updated: '2026-08-20T23:34:46.290Z' +updated: '2026-08-20T23:46:37.574Z' reviewStatus: approved +publishedAt: '2026-08-20T23:35:35.277Z' reviewBasis: technical-publication-authorization implementationReviewedBy: Co -implementationReviewedAt: '2026-08-20T23:35:35.277Z' +implementationReviewedAt: '2026-08-20T23:48:14.923Z' publicationAuthorization: kind: technical-publication-authorization authorizedBy: Cameron - recordedAt: '2026-08-20T23:15:52Z' + recordedAt: '2026-08-20T23:46:37.574Z' route: letta-office-hours-2026-08-20 scope: technical-publication exactRenderReviewed: false receiptPath: knowledge/receipts/technical-publication/letta-office-hours-2026-08-20.json - receiptDigest: 'sha256:fbbfda00a13f8ddf1c9e78ce9bd289ad572aeca1c0229810ea900fa6cc3c260e' -publishedAt: '2026-08-20T23:35:35.277Z' -reviewedContentDigest: 'sha256:abd7d9938579804cd0ef7879a1300670894d8cde6dcfc37988cef35323718393' -reviewReceiptDigest: 'sha256:fbbfda00a13f8ddf1c9e78ce9bd289ad572aeca1c0229810ea900fa6cc3c260e' + receiptDigest: 'sha256:46a24f4111958ae35827650821421a521ec8f2e6c199e037e0994ab551fceb4a' +reviewedContentDigest: 'sha256:f047d295dcf58ae414aab8760f60340e804e6a8e8db48e9126403457c2fa37b1' +reviewReceiptDigest: 'sha256:46a24f4111958ae35827650821421a521ec8f2e6c199e037e0994ab551fceb4a' --- The [August 20, 2026 Letta Office Hours episode](https://www.youtube.com/watch?v=luCpXx4JjCk) begins with hosted Slack agents, a live view into an agent's cloud computer, GLM 5.3, provider quota controls, and a Signal-based Agent SDK client. The community Q&A then moves through computer use, model routing, agent orchestration, mobile clients, cloud sandboxes, teleportation, and compaction. @@ -107,7 +107,7 @@ This guide is part of the [Letta Office Hours archive](/knowledge/letta-office-h Letta now hosts the Slack connection for Cloud agents, so teams do not need to run their own channels listener. A user selects an existing agent in the Letta web interface, authorizes a Slack app, and then talks to that agent through direct messages or channel mentions. The [channels documentation](https://docs.letta.com/letta-code/channels) distinguishes this native path from self-operated channel adapters. -The setup preserves Slack's own boundaries. An agent app must be added to each channel before it can respond there. A message can link back to the corresponding conversation in Letta's web interface, where the operator can inspect the agent and its context more directly. +Slack still controls channel access. An agent app must be added to each channel before it can respond there. A message can link back to the corresponding conversation in Letta's web interface, where the operator can inspect the agent and its context more directly. Each Slack thread can create a separate conversation backed by its own cloud sandbox. One agent can therefore work on several tasks at once without merging their message histories. Those conversations still share the agent's retained memory. [Letta](/knowledge/letta) uses the same distinction throughout: the agent is the continuing entity, while a conversation is one thread with that entity. @@ -119,7 +119,7 @@ The next demo opens a computer panel in Letta Chat and Desktop. The panel shows The panel makes cloud computer use easier to supervise during interface development, browser work, and visual testing. Cameron shows a file created by an agent and a small web application produced inside the sandbox. The generated application is incidental. The panel lets someone see the task environment without moving the conversation onto their own computer. -The [computers documentation](https://docs.letta.com/platform/computers/) defines the boundary precisely. A computer provides a shell, files, credentials, installed software, and local tools. Agent identity and memory live separately. A live desktop view improves observation of the computer, while tool results and run state remain the stronger record of what the agent actually changed. +The [computers documentation](https://docs.letta.com/platform/computers/) defines what belongs to a computer: a shell, files, credentials, installed software, and local tools. Agent identity and memory live separately. A live desktop view improves observation of the computer, while tool results and run state remain the stronger record of what the agent actually changed. Computer use does not require a unique Letta-only mechanism. In the Q&A, Cameron describes screenshot-driven skills and test harnesses that pre-program interactions and return contact sheets for review. He also recommends delegating specialized computer-use work to coding harnesses that already have strong support for it. The persistent agent can decide when to call those harnesses without pretending their native capabilities belong to Letta itself. @@ -165,9 +165,9 @@ Delegation does not merge the systems. Each harness still has its own tool behav Cameron's [tangled-letta](/knowledge/tangled-letta) example applies the same pattern inside continuous integration. A Tangled pipeline starts a persistent Cloud agent in a separate sandbox, asks it to inspect an exact public commit, and validates streamed tool evidence against runner-owned expectations. The pipeline remains responsible for deciding whether the agent's observations satisfy the job. -## Agent communication crosses the isolation boundary +## Agent communication creates a cross-organization data path -A question about communication between agents in separate Letta organizations produces the episode's sharpest security discussion. Separate organizations can isolate data because their agents, memory, and credentials do not share one authority domain. Connecting those agents creates an information path across that boundary. +A question about communication between agents in separate Letta organizations produces the episode's sharpest security discussion. Separate organizations can isolate data because their agents, memory, and credentials do not share one authority domain. Connecting those agents creates an information path between them. In the Q&A, Cameron argues that strict data isolation no longer exists once agents can exchange messages. An agent may reveal memory directly, summarize sensitive context, or expose information indirectly through ordinary conversation. Accidental disclosure is enough to break the original security claim. @@ -203,11 +203,11 @@ The episode connects five layers that often collapse into the word “agent”: 2. **Conversation:** one message history, queue, permission mode, and execution placement. 3. **Computer:** the shell, filesystem, credentials, tools, and processes used for work. 4. **Client:** the Slack thread, web chat, desktop shell, mobile app, or CI runner that presents and invokes the conversation. -5. **Authority boundary:** the organization, sharing rule, machine permission, and approval policy that determines who may cause which effects. +5. **Authority:** the organization, sharing rule, machine permission, and approval policy that determines who may cause which effects. Hosted Slack, the computer panel, Signal Desktop, Bloop, and teleportation are easier to understand when those layers stay distinct. A simple client can hide configuration without becoming the identity owner. A conversation can move computers without copying every file or credential. One agent can supervise several harnesses without those harnesses sharing one runtime. Two agents can communicate only by opening a channel that deserves its own security model. -The product direction places simpler surfaces over a more explicit runtime. Stable boundaries have to supply that simplicity; hiding a boundary does not remove it. +The product direction places simpler surfaces over a more explicit runtime. Stable contracts have to supply that simplicity; hiding a permission rule or runtime split does not remove it. ## Evidence limits diff --git a/knowledge/published/letta-office-hours.md b/knowledge/published/letta-office-hours.md index bed1351..9efc303 100644 --- a/knowledge/published/letta-office-hours.md +++ b/knowledge/published/letta-office-hours.md @@ -30,23 +30,23 @@ sources: aiAssisted: true generatedBy: Co sourceDigest: 'sha256:ab454983eb6710b2af168717c94138024c01b1d97c594a4aeeec65764f7c10e3' -updated: '2026-08-20T23:34:46.290Z' +updated: '2026-08-20T23:46:37.574Z' reviewStatus: approved +publishedAt: '2026-08-07T02:41:18.752Z' reviewBasis: technical-publication-authorization implementationReviewedBy: Co -implementationReviewedAt: '2026-08-20T23:35:44.494Z' +implementationReviewedAt: '2026-08-20T23:48:15.511Z' publicationAuthorization: kind: technical-publication-authorization authorizedBy: Cameron - recordedAt: '2026-08-20T23:15:52Z' + recordedAt: '2026-08-20T23:46:37.574Z' route: letta-office-hours scope: technical-publication exactRenderReviewed: false receiptPath: knowledge/receipts/technical-publication/letta-office-hours.json - receiptDigest: 'sha256:e097216e9c95d48fb8632298968ba7818fc32fdd55dce8c9d44d451ba990f391' -publishedAt: '2026-08-07T02:41:18.752Z' -reviewedContentDigest: 'sha256:57c096616cfb55aebb0b25fcd2482943eed197163de91da718495545b9456cd7' -reviewReceiptDigest: 'sha256:e097216e9c95d48fb8632298968ba7818fc32fdd55dce8c9d44d451ba990f391' + receiptDigest: 'sha256:47c6ed9f4799eb7a6ef8fc32660feb85e45211866984a20037e72380e7a5c924' +reviewedContentDigest: 'sha256:f3c27c82bc5400272268d454c9963ddc01113adc0cbb71e9d4e909c877a6a6ef' +reviewReceiptDigest: 'sha256:47c6ed9f4799eb7a6ef8fc32660feb85e45211866984a20037e72380e7a5c924' --- Letta Office Hours is Letta's weekly livestream about building and using persistent agents. Cameron usually opens with recent product changes and a working demo, sometimes brings in a Letta team member to explain a product surface or decision, and then leaves most of the room for audience questions. Episodes move freely between release notes, technical architecture, community projects, failure reports, and the practical experience of keeping one agent over time. @@ -73,7 +73,7 @@ The pages are historical records, not current product manuals. Letta changes qui ### 2026 -- **[2026-08-20: Cloud Agents in Slack, Computer Use, GLM 5.3, and Custom Clients](/knowledge/letta-office-hours-2026-08-20)** — Hosted Slack agents, live cloud-computer views, model-provider updates, custom Agent SDK clients, orchestration, teleportation, and agent-to-agent security boundaries. +- **[2026-08-20: Cloud Agents in Slack, Computer Use, GLM 5.3, and Custom Clients](/knowledge/letta-office-hours-2026-08-20)** — Hosted Slack agents, live cloud-computer views, model-provider updates, custom Agent SDK clients, orchestration, teleportation, and cross-organization information-flow risks. - **[2026-08-13: Dynamic Workflows, Cloud Agents, Grok 4.6, and Personalized Software](/knowledge/letta-office-hours-2026-08-13)** — Agent SDK examples, dynamic workflows, cloud sandboxes, MemFS retrieval, application architecture, and software built around persistent agents. @@ -99,7 +99,7 @@ The pages are historical records, not current product manuals. Letta changes qui - **[2026-05-08: Sandboxes for Letta Chat, Sensemaker, and an agent that plays Pokemon](/knowledge/letta-office-hours-2026-05-08)** — New channel controls, local-only Letta Code, sandboxed agents in Letta Chat, Sensemaker, and design guidance for building durable agents. -- **[2026-05-01: Discord Channel, Custom Plugins, Letta City Sim, and a Special Guest](/knowledge/letta-office-hours-2026-05-01)** — Office hours covers Discord channels, custom plugins, schedules, policy boundaries, Letta City Sim, model updates, and a long Q&A on memory, context, and agents. +- **[2026-05-01: Discord Channel, Custom Plugins, Letta City Sim, and a Special Guest](/knowledge/letta-office-hours-2026-05-01)** — Office hours covers Discord channels, custom plugins, schedules, policy controls, Letta City Sim, model updates, and a long Q&A on memory, context, and agents. - **[2026-04-23: Digital Coworkers with Slack](/knowledge/letta-office-hours-2026-04-23)** — Letta office hours on Slack-native agents, remote environments, channel hosting, and why skills beat MCP-style integrations. diff --git a/knowledge/receipts/technical-publication/letta-office-hours-2026-08-20.json b/knowledge/receipts/technical-publication/letta-office-hours-2026-08-20.json index f5fb6be..6d85830 100644 --- a/knowledge/receipts/technical-publication/letta-office-hours-2026-08-20.json +++ b/knowledge/receipts/technical-publication/letta-office-hours-2026-08-20.json @@ -4,9 +4,9 @@ "entrySlug": "letta-office-hours-2026-08-20", "route": "letta-office-hours-2026-08-20", "authorizedBy": "Cameron", - "recordedAt": "2026-08-20T23:15:52Z", + "recordedAt": "2026-08-20T23:46:37.574Z", "scope": "technical-publication", - "authorizationBasis": "Telegram message 18382 supplied the August 20 Office Hours transcript and YouTube URL and explicitly requested a Public Knowledge document. Message 18384 confirmed that the video was public.", + "authorizationBasis": "Telegram message 18382 supplied the August 20 Office Hours transcript and YouTube URL and explicitly requested a Public Knowledge document. Message 18384 confirmed that the video was public. Message 18387 asked that ‘boundaries’ be reserved for uses where it names an actual system property; this revision replaces generic occurrences while preserving the official chapter title.", "exactRenderReviewed": false, "implementationReviewedBy": "Co", "constraints": [ diff --git a/knowledge/receipts/technical-publication/letta-office-hours.json b/knowledge/receipts/technical-publication/letta-office-hours.json index 41cd7d1..588bab7 100644 --- a/knowledge/receipts/technical-publication/letta-office-hours.json +++ b/knowledge/receipts/technical-publication/letta-office-hours.json @@ -4,9 +4,9 @@ "entrySlug": "letta-office-hours", "route": "letta-office-hours", "authorizedBy": "Cameron", - "recordedAt": "2026-08-20T23:15:52Z", + "recordedAt": "2026-08-20T23:46:37.574Z", "scope": "technical-publication", - "authorizationBasis": "Telegram message 18382 supplied the August 20 Office Hours transcript and YouTube URL and explicitly requested a Public Knowledge document. Updating the chronological Office Hours map is part of making that commissioned guide discoverable.", + "authorizationBasis": "Telegram message 18382 supplied the August 20 Office Hours transcript and YouTube URL and explicitly requested a Public Knowledge document. Updating the chronological Office Hours map is part of making that commissioned guide discoverable. Message 18387 asked that ‘boundaries’ be reserved for uses where it names an actual system property; this revision updates the map summary accordingly.", "exactRenderReviewed": false, "implementationReviewedBy": "Co", "constraints": [