[maxy-shpfy]

Description

Gives every Tangent session in a project a shared, persistent memory so later sessions build on what earlier ones learned, instead of each session starting cold with its own private store.

On the first session start in a project, a Tangent shared folder is provisioned and its id is saved in the project metadata (tangentSharedFolderId); subsequent sessions reuse it. Each session then mounts that folder as project/ and binds a composite memory — a human-readable simple-md note under project/NOTES plus a pi-memory store under project/pi-memory — so memory_* tool writes and files are visible across all sessions in the project. When a shared folder exists, the session's standing memory seed also includes a brief explaining how to use it (record decisions/conventions with memory_write, memory_search before re-deriving, keep project/NOTES/MEMORY.md current, never write secrets).

Provisioning is defensive: it reads project metadata from the server (not the cache) because the PATCH replaces the whole metadata object, and re-reads after creating the folder so a folder another tab saved in the meantime wins rather than splitting memory across two stores. The mutation uses a per-project scope so concurrent starts run one at a time and reuse the first folder. Any failure (missing base URL/token, Tangent or project API refusal) resolves to undefined so the session still starts — just without the shared folder.

Also bumps the @tangent/* dependencies from main to a pinned commit that provides the pi-memory memory binding support.

Related Issue and Pull requests

Type of Change

• New feature

Line Breakdown

Category	Added	Removed
Production code	209	3
Comments	26	1
Tests	376	0
Config / CI / tooling	4	4
Generated / lockfiles	277	277
Total	892	285

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Screenshots (if applicable)

Tangent.-.Project.memory.preview.mp4

Test Instructions

1. Open a project and start a new Tangent session; confirm the project metadata gains a tangentSharedFolderId.
2. In that session, use memory_write to record something, then start a second session in the same project and confirm memory_search surfaces it and files written under project/ are visible.
3. Start two sessions in quick succession and confirm only one shared folder is created (reused, not duplicated).
4. Simulate a shared-folder creation failure (e.g. revoke the token) and confirm the session still starts without a shared folder.

Additional Comments

[github-actions]

🎩 Preview

A preview build has been created at: maxy/feat--use-pimemory-in-projects/5e388a5

[maxy-shpfy]

This changes are TMP just for tophatting - will be reverted before merge as soon as shell PR TangleML/tangent-shell#145 landed

[maxy-shpfy]

AI facilitated response

Still open: the @tangent/* pin to 8f2c11c is still in package.json (the three dependencies and the pnpm.overrides entry). Leaving this unresolved until TangleML/tangent-shell#145 lands and the pin is switched to its merge commit on main, or back to #main.

[camielvs]

🤖 This is an AI-generated code review comment.

4 findings inline (1 high, 2 medium, 1 low). CI is green; GitHub reports a conflict in pnpm-lock.yaml with master (from #2979), so this needs a rebase.

Cross-repo, for TangleML/tangent-shell#145: shared folders have no access checks there. GET /api/shared-folders returns every folder with its id, and applyMount doesn't check who's asking, so anyone using the same Tangent server could mount another project's shared memory, including projects in workspaces they don't belong to. The fix belongs in tangent-shell, but this PR is the first to write project knowledge into those folders, so it's worth confirming they get the same access limits as sessions before this ships.