# /zibby-memory-pull — pull the team's latest test memory from the configured remote You are helping the user fetch the team's latest learnings (selectors, page model, insights, run history) from the project's configured memory remote into local `.zibby/memory/.dolt/`. Canonical docs: **https://docs.zibby.app/tests/memory** ## When this is needed (vs. just runs automatically) `zibby test` auto-pulls before every run when a remote is configured, and auto-pushes after every passing run. So most of the time the user doesn't need to invoke pull manually. Manual pull is for: - Fresh clone of the repo — first sync to seed `.zibby/memory/.dolt/` from the remote - After a teammate landed a big batch of new learnings and the user wants them before running anything - Inspecting team memory (`/zibby-memory-stats`, `/zibby-memory-cost`) without running a test - Reconciling after a manual conflict in the Dolt DB ## How to run ``` Bash(zibby memory pull) ``` The CLI fetches from whatever remote `zibby memory remote info` reports — BYO S3/GCS/DoltHub URL or the Zibby-hosted backend. No flags. ## Pre-flight: is a remote configured? Before suggesting `pull`, check: ``` Bash(zibby memory remote info) ``` - **No remote configured** → pull errors out. Tell the user to either: - Add their own: `zibby memory remote add aws://my-bucket/team/proj/main` - Use the hosted one: `zibby memory remote use --hosted` (requires `zibby login`) - See `/zibby-memory-remote-use-hosted` for the hosted path. - **Hosted remote, signed out** → `zibby login` first. ## After pulling Confirm the pull landed with `/zibby-memory-stats` — row counts should jump (selectors, runs, insights) compared to before. ## Related - `zibby memory push` — manual push (auto on passing test, but sometimes you want to share now) - `/zibby-memory-stats` — verify what came in - `/zibby-memory-remote-use-hosted` — switch to the Zibby-managed S3 backend