Skip to content

feat(memory): carry bot-owned notes across chats - #293

Merged
leoisadev1 merged 6 commits into
mainfrom
resume-memory-solution
Sep 19, 2026
Merged

leoisadev1 merged 6 commits into
mainfrom
resume-memory-solution

Conversation

@leoisadev1

@leoisadev1 leoisadev1 commented Sep 19, 2026

Copy link
Copy Markdown
Member

Bots need small, editable notes that carry useful context into later chats. This replaces saved facts with bot-owned USER.md and MEMORY.md files and separate GROUP.md notes for each group. Chat observations remain separate.

Memory is supplied on every turn, with enforced file limits and a review after ten successful prompts in each private or group scope. Recent context now keeps 30 complete turns within a roughly 64,000-token budget, retaining messages that observations have not covered. Web and mobile memory editors support direct changes, and archive import/export preserves notes and observations. Approved legacy facts migrate once; unsupported or overflowing facts remain in an archive.

The final fixes bound hand-edited prompt context, reject stale saves and changed bot ownership, reject cross-chat archive restores, and preserve pending observations. Failed imports roll back file and observation changes; queued observation writes cannot be erased by a stale restore. Failed lock initialization releases its handle and lock before retry.

Verified with 442 focused tests, server/web/mobile/contracts/client-runtime typechecks, targeted lint, browser save/reload/clear and archive round-trip, and real GPT-5.6 Sol conversations. The live cadence test completed ten prompts and verified one successful review call on turn eleven. Automated-review fixes passed 208 focused tests, including real LibSQL restore failure and stale-preview cases, plus browser stale-save rejection and archive restoration. Native mobile device execution and live calls through other providers were not tested. Desktop uses the shared web renderer; no Electron shell behavior changed.

Before After
Saved facts panel Editable bot memory files

Created with GPT-6 Astra in Codex.


Devin Review

@github-actions github-actions Bot added type:provider Agent provider contribution. area:connectors Plugin and MCP connector runtime. vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:XXL labels Sep 19, 2026
devin-ai-integration[bot]

This comment was marked as resolved.

@greptile-apps

greptile-apps Bot commented Sep 19, 2026

Copy link
Copy Markdown

RetriggerConfidence Score: 5/5

Safe to merge.

Summary

This PR adds bot-owned Markdown memory documents, conversation observations, archive import/export, memory review scheduling, client editing flows, and supporting authorization and provider-context integration.

Reviews (3) · Last reviewed commit: "fix(memory): require MCP memory capabili..."

greptile-apps[bot]

This comment was marked as resolved.

@greptile-apps

This comment has been minimized.

devin-ai-integration[bot]

This comment was marked as resolved.

greptile-apps[bot]

This comment was marked as resolved.

@leoisadev1
leoisadev1 merged commit 1c1dada into main Sep 19, 2026
10 checks passed
@leoisadev1
leoisadev1 deleted the resume-memory-solution branch September 19, 2026 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:connectors Plugin and MCP connector runtime. size:XXL type:provider Agent provider contribution. vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant