letta-code — what enters each provider call (local backend)

letta-code — what enters each provider call (local backend) A data-flow diagram generated by Archify. 01 / Sources 02 / Client shaping 03 / State on disk 04 / Per-call request 05 / Model User prompt · turn input · 01 / Sources User prompt turn input Turn input · + reminder parts · 02 / Client shaping Turn input + reminder parts Transcript · append-only (recall) · 03 / State on disk Transcript append-only (recall) Message view · summary + tail · 04 / Per-call request Message view summary + tail Raw tool output · Bash · Read · … · 01 / Sources Raw tool output Bash · Read · … Clamp + scrub · ≤ 32k chars, head+tail · 02 / Client shaping Clamp + scrub ≤ 32k chars, head+tail Overflow file · full output on disk · 03 / State on disk Overflow file full output on disk Compaction · > window − 16k reserve · 04 / Per-call request Compaction > window − 16k reserve MemFS repo · committed HEAD only · 01 / Sources MemFS repo committed HEAD only Compiled prompt · cached; Δ on new commit · 03 / State on disk Compiled prompt cached; Δ on new commit System prompt · + <available_skills> · 04 / Per-call request System prompt + <available_skills> Model · one pi-ai Context · 05 / Model Model one pi-ai Context Skills · SKILL.md frontmatter · 01 / Sources Skills SKILL.md frontmatter Request extras · client_tools/skills · 04 / Per-call request Request extras client_tools/skills prompt append tool_return approval msg full text in-context summary + tail HEAD at create/compact same bytes name + description messages system tool schemas Legend primary data side write (not in context) data store data flow