Documentation
How Project Memory Works
A practical guide to project context, sessions, collaboration, GitHub, the official CLI, and review-first AI features.
Guide contents
Section 1
Getting Started
Create a project, capture its working context, and return to useful information instead of reconstructing it.
Create or import a project
Start blank, use a built-in template, or import a Project Memory export when your plan allows it.
Capture the current state
Set Current Status, Next Action, and Important Context, then add tasks or issues for concrete work.
Work from web or terminal
The web app and official CLI use the same projects, sessions, activity, and Project Memory.
Section 2
Project Memory
Project Memory is the compact context layer that answers where the project stands, what comes next, and what must not be forgotten.
Shared context
Project members see one shared memory state rather than maintaining separate handoff documents.
Intentional updates
Memory fields change only when you edit them or publish a reviewed update. Ordinary navigation does not rewrite memory.
Section 3
Current Status, Next Action, Important Context, and Open Issues
These fields divide project context into clear, practical responsibilities.
Current Status
Capture where the project stands so you can resume with confidence.
Next Action
Write the next move directly, create and link a task, or link an existing task or issue.
Important Context
Keep constraints, assumptions, architectural reminders, and other durable context close to the work.
Open Issues
Track project-level blockers and known problems alongside the memory they affect.
Section 4
Sessions
A session groups meaningful work into a reviewable block with a clear beginning and finalized record.
Web sessions
The first meaningful project change starts a session automatically after the previous session has ended. Viewing, navigation, and search do not start one.
CLI sessions
Running pm resume creates or resumes the same active backend session used by the web app.
Individual work, shared project
Collaborators have individual sessions while working against the same project context and history.
Section 5
Resume
Resume brings the most useful current context to the surface before you begin another block of work.
Web workspace
Open a project to review its memory, open work, recent session, and GitHub context without changing project status.
Terminal workflow
Use pm resume to show the project name, session state, memory fields, open issues, and open tasks.
pm resume
Smart Resume
When eligible, an optional AI Assist can draft a resume brief. It requires confirmation and never silently changes Project Memory.
Section 6
End Session and Handoff
End Session reviews recorded work and saves a factual handoff without asking you to recreate activity the app already knows.
Session Review
Review completed tasks, resolved issues, commits, closed GitHub issues, changed files, discussions, outcomes, and optional notes associated with the session.
Web flow
The web drawer finalizes the session first, then offers a gentle optional Project Memory update.
CLI flow
pm session end uses the same review and finalization services, with optional terminal prompts for memory review.
pm session end
Smart Handoff
An optional AI Assist can draft a handoff after deterministic review. You choose whether to publish any suggested memory changes.
Section 7
Tasks and Issues
Use tasks for executable work and issues for project-level blockers or problems that affect context.
Tasks
Prioritize, schedule, snooze, assign, complete, reopen, and optionally connect completed work to Git commits.
Issues
Create, resolve, reopen, or link issues as Next Action while preserving resolution history.
Linked Next Action
When linked work changes title or becomes unavailable, Project Memory keeps the relationship understandable and offers a gentle review prompt.
Section 8
Notes, Decisions, and Links
Keep supporting knowledge separate from the compact memory fields while preserving it inside the project.
Notes
Capture reference material, investigation results, and working observations.
Decisions
Record what was decided, why it matters, and the project context related to it.
Links
Keep documentation, designs, deployments, and other project resources easy to find.
Section 9
GitHub
Connect a repository so code activity can appear beside the project context it belongs to.
Repository activity
Review commits, pull requests, GitHub issues, and changed files without exporting credentials or installation metadata.
Branches and sync windows
Automatic commit and changed-file sync follows the connected repository activity available from GitHub. Work that exists only in a local branch is not visible until it is pushed.
Task and issue links
Import GitHub issues as tasks and link commits to completed tasks while preserving local Project Memory workflows.
Repository management
Connection and repository management stay in the web app; the CLI can use local Git context for matching and commit links.
Section 10
Collaboration and Team
Invite people into a shared project while keeping ownership, plan capacity, and permissions explicit.
Roles
Free includes limited collaboration, while paid plans increase collaborative-project and member capacity. Owners can invite Full Access members or Contributors, with the same backend permissions enforced for web and CLI.
Assignments and attribution
Assign tasks and preserve who created, updated, completed, or resolved collaborative work.
Owner plan
The project owner's plan controls collaborative capacity. Shared projects do not count as owned projects for collaborators.
Section 11
Discussions
Use project discussions for focused collaboration that should remain connected to the work it concerns.
Linked conversations
Start discussions from supported tasks, issues, decisions, Project Memory fields, or GitHub issues where available.
Discussion Outcome
Resolve a discussion with a summary and optionally preserve the outcome as a task, issue, or decision.
AI refinement
Eligible plans can use an optional AI Assist to draft a discussion outcome for review before resolution.
Section 12
Official CLI
The CLI is another interface to the same backend, designed for developers who want to stay in the terminal.
Install and authenticate
Install with pipx, authorize a device in the browser, and use pm doctor when configuration needs checking.
pipx install projectmemory-cli
Everyday work
Resume projects, manage tasks and issues, capture notes, update memory, link commits, and end sessions.
Full command reference
The CLI Dashboard contains searchable commands, examples, device status, quick start, and troubleshooting.
Section 13
AI Features
AI Assists are optional, metered, review-first tools rather than automatic changes to project data.
Explicit confirmation
Project Memory shows the feature, available balance, and expected cost before generation.
Draft before publish
Smart Resume, Smart Handoff, and discussion outcome assists return drafts that remain separate until you approve them.
Shared accounting
Usage is charged to the project owner and records the feature, project, and collaborator who initiated it.