# Record **Author:** @cameron.stream (`did:plc:gfrmhdmjvxn2sjedzboeudef`) ## `knowledge-letta-office-hours-2026-07-16` **Collection:** `site.standard.document` **AT URI:** `at://did:plc:gfrmhdmjvxn2sjedzboeudef/site.standard.document/knowledge-letta-office-hours-2026-07-16` **Title:** Letta Office Hours: Cloud Sandboxes, GitHub Integration, GPT-5.6, and Agent Sharing **Published:** Fri, 07 Aug 2026 02:41:34 GMT **Updated:** Fri, 21 Aug 2026 03:27:30 GMT **Description:** Letta adds persistent cloud sandboxes, GitHub integration, model support updates, and a broader discussion of shared and cross-organizational agents. **Publication:** `at://did:plc:gfrmhdmjvxn2sjedzboeudef/site.standard.publication/3mr4py6clps2f` **Path:** /letta-office-hours-2026-07-16 **Tags:** knowledge, journal, ai, agents, letta, office-hours, public-source, cloud-sandboxes, git, agent-sharing, openai-compatible-apis **Content:** ```json { "text": "[Watch this episode on YouTube]()\n\nThe [July 16, 2026 Letta Office Hours episode](https://www.youtube.com/watch?v=vOOoH2QEEFg) covers persistent Cloud sandboxes, GitHub integration, model-provider support, schedules, and agent sharing. The guest discussion with Shub separates the agent's retained identity from the sandbox, model, schedule, and organization through which it works.\n\nThis guide is part of the [Letta Office Hours archive](https://cameron.stream/knowledge/letta-office-hours). It records the product and design discussion from that date; current behavior belongs in the [Letta documentation](https://docs.letta.com/).\n\n## Selected chapters\n\n| Time | Topic |\n| --- | --- |\n| [00:00](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=0s) | Intro and framing |\n| [00:46](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=46s) | Persistent Cloud sandboxes |\n| [03:14](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=194s) | Sandbox archival and retention |\n| [03:48](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=228s) | GitHub integration |\n| [05:23](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=323s) | Mods repository updates |\n| [06:48](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=408s) | GPT-5.6, Grok 4.5, and custom endpoints |\n| [08:43](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=523s) | Shub joins the episode |\n| [11:06](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=666s) | Design process with Tonic |\n| [11:38](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=698s) | Personal, shared, and cross-organization agents |\n| [16:16](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=976s) | Cloud scheduling and performance improvements |\n| [19:51](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=1191s) | Persistent sandbox demo begins |\n| [27:54](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=1674s) | Constellation and non-Constellation agents |\n| [34:16](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=2056s) | What “local agent” means |\n| [39:20](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=2360s) | ATProto and inter-agent communication |\n| [53:21](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=3201s) | Migrating between Cloud and local agents |\n| [1:11:08](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=4268s) | New-user experience and companion guides |\n| [1:24:09](https://www.youtube.com/watch?v=vOOoH2QEEFg&t=5049s) | Misaligned and game design |\n\n## Persistent sandboxes retain the working computer\n\nThe episode presents a Cloud sandbox as a writable environment whose files survive beyond one interaction. An agent can continue work without asking the user to provision a separate remote machine for each task.\n\nPersistence changes what the system must track. The agent retains identity and memory; the sandbox retains files and installed tools. Archival and retention rules decide how long that computer remains available. GitHub integration brings a repository into the sandbox so the agent can inspect and modify code in the same environment.\n\n## Model providers can change without moving agent state\n\nThe product update includes additional models and a general OpenAI-compatible endpoint for custom providers. These integrations let the harness retain the agent and conversation while routing inference through a different model service.\n\nModel portability does not make providers interchangeable. Tool behavior, context limits, latency, cost, and model quality can still differ. The stable part is the surrounding agent state and application interface.\n\n## Sharing assigns an agent to a scope\n\nShub distinguishes personal, shared, and cross-organization agents. A personal agent belongs to one user. A shared agent serves a group. A cross-organization agent may relay work between groups that otherwise keep separate systems.\n\nThose roles require access rules and data-flow decisions. Copying a chat transcript would preserve messages but lose the continuing identity, memory, tools, and permissions associated with the agent. Sharing therefore needs an explicit answer to who can invoke the agent, which context it can read, and where its outputs may travel.\n\n## Schedules return to retained state\n\nCloud scheduling lets an agent resume work after the user's immediate session ends. The schedule supplies a time and prompt. The agent and sandbox supply the retained context and files needed to continue.\n\nThe episode also discusses performance work because persistent workflows become unpleasant if every return to the agent is slow. Latency and reliability are operating constraints on the architecture, not separate product polish.\n\n## Local and Cloud describe several placements\n\nThe Q&A shows why “local agent” is ambiguous. Memory, inference, tools, files, and the client interface can each live in a different place. Moving between Cloud and local operation therefore requires naming which component moves and which state remains behind.\n\nThe same precision applies to cross-organization communication. An inter-agent protocol can transport messages, but the organizations still need policies for identity, access, provenance, and disclosure. The ATProto discussion explores one possible protocol layer; it does not eliminate those application decisions.\n\n## Experiments expose interaction assumptions\n\nThe episode discusses companion guides for newcomers and the Misaligned game project. Both are ways to test whether users understand where an agent's work and state live. A guide teaches the model directly. A game can make agent behavior and human assumptions visible through play.\n\nThese examples sit outside the core sandbox demo, but they address the same product problem: persistent systems need a legible mental model. A user should be able to tell which agent is acting, which environment it occupies, and which organization grants its access.\n\n## The agent, sandbox, model, schedule, and organization remain separate\n\nThe episode's product updates fit together once those objects stay distinct. A sandbox can persist while the model changes. A schedule can invoke an existing agent. A repository can enter one sandbox without becoming part of the agent's identity. Sharing can widen access to the agent without granting every participant access to every environment.\n\nThis separation gives the product more deployment options. It also requires explicit interfaces between the layers; changing one layer should not silently widen another layer's authority.\n\n## Public sources\n\n- [YouTube episode](https://www.youtube.com/watch?v=vOOoH2QEEFg)\n- [Letta documentation](https://docs.letta.com/)\n- [Agent Client Protocol](https://docs.letta.com/platform/acp)\n- [Letta Agent SDK](https://docs.letta.com/agent-sdk)\n- [Letta Code](https://github.com/letta-ai/letta-code)\n- [Letta ACP repository](https://github.com/letta-ai/letta-acp)\n\n## Sources\n\n- [Official YouTube episode]()\n- [Letta documentation]()", "$type": "site.standard.content.markdown", "version": "1.0" } ``` --- *Fetched from https://enoki.us-east.host.bsky.network via `com.atproto.repo.getRecord`*