Skip to main content

Memory & Projects

Memory is private, Cloud-backed state — separate from Skills, and never implied to be part of a public STAK. See Sharing for the full boundary of what a published STAK does and does not contain.

How Memory works

Memory is an agent's accumulated private context on this machine. STAK can discover it, back it up into its own private store, and later restore it — all read-only with respect to your agent's native files; backup never modifies them.

stak memory scan
stak memory backup
stak memory status

Stable logical Project identity

A Project is a stable logical identity in STAK Cloud, derived from recovered Memory — not a folder. Renaming or moving the local directory you work in never changes a Project's identity; the directory is only ever a machine-specific binding to it.

stak project

Local machine mappings

Mapping a Project to a directory authorizes that directory as the restore destination for it on this machine. The mapping is local only — the path is never shared as the Project's identity, and is refused when the directory already belongs to a different repository or a different logical Project.

stak project map my-app ~/code/my-app

Backup/recovery

Back up when you want Memory durably stored; restore writes only absent targets — a differing existing target is reported as a conflict and left untouched, never merged over.

stak memory backup
stak memory restore

Moving to another computer

On a new machine, sign in and pull — this restores your desired Environment and your latest staged private Memory generation in one step. If you use Claude Code, materialize that Memory into it, then map any Project that can't reconcile automatically:

stak login
stak pull
stak project
stak memory restore --dry-run
stak memory restore
stak project map my-app ~/code/my-app

stak memory recover is the explicit/history recovery path — reach for it when you need an older generation or Memory outside the normal pull flow, not as a routine step after pull.

Memory is currently scoped to Claude Code; Codex and Cursor memory support is planned.