Pricing
Choose your Project Memory plan.
Start free, then upgrade when you need more owned projects, collaboration capacity, or AI assists.
Get Pro for $4/month or $40/year.
Lock this rate while your subscription remains continuously active.
Free
For getting one focused workspace into motion.
$0
Forever
- ✓2 owned projects
- ✓2 collaborative projects, 1 collaborator/project
- ✓Project Memory workflow
- ✓Tasks, issues, notes, decisions, sessions
- ✓GitHub integration and official CLI
Pro
For developers and small teams with multiple projects.
$8/month
$80/year annually
- ✓Everything in Free
- ✓Unlimited owned projects
- ✓Collaborate across up to 5 projects
- ✓Up to 3 collaborators per project
- ✓10 AI Assists/month
- ✓Roles, discussions, assignments, and history
Team
For collaboration plus AI-assisted handoffs.
$19/month
Monthly during AI Early Access
- ✓Everything in Pro
- ✓Collaborate across up to 20 projects
- ✓Up to 10 collaborators per project
- ✓100 AI Assists/month
- ✓AI Smart Handoff and AI Smart Resume
Scale
For larger project teams with heavier AI usage.
$49/month
Monthly
- ✓Everything in Team
- ✓Unlimited collaborative projects
- ✓Up to 30 collaborators per project
- ✓300 AI Assists/month
- ✓Contact us if you need more than 30 collaborators
Project-based collaboration. Plans define collaborative projects and collaborators per project.
Documentation
How Project Memory Works
Everything you need to understand the product — from first login to daily developer workflows, team collaboration, GitHub integration, and the CLI.
Quick Start
Get from zero to your first project context in under five minutes.
-
1
Create an account
Register at projectmemory.app/register. No credit card required.
-
2
Create a project
Give your project a name and an optional description. Choose a system template or start blank.
-
3
Fill in Project Memory
Set Current Status, Next Action, and Important Context. These three fields are the core of what the product stores for you.
-
4
Do the work
On the web, the first meaningful project change starts a session automatically. In the CLI,
pm resumestarts or resumes it. End the session when you finish to preserve a factual review of what changed.
Tip: use the CLI to resume from the terminal
Install the CLI and run pm resume to see current status and next action without opening the browser.
Project Memory
Project Memory is the structured context snapshot for each project. It answers the questions every developer asks when resuming: Where did we stop? What needs to happen next? What should I keep in mind?
Current Status
Where the project stands right now
A plain-text description of the present project state. Updated manually or as part of an end-session review.
Next Action
The single most useful move
Set it manually or link it directly to an existing task or issue. When it is empty, Today's Focus can offer the most actionable open task, falling back to an open issue when no task is available.
Important Context
The why behind the work
Constraints, assumptions, key decisions, and architectural reminders. Anything that someone picking up the project needs to know before touching the code.
Open Issues
What still needs attention
Unresolved blockers and known bugs tracked alongside the context they affect. An open issue may be linked explicitly as the Next Action or suggested when there are no actionable tasks.
How updates work
Each Memory field is edited inline on the Memory tab. Changes are saved immediately. The CLI equivalent is pm memory show and pm memory update.
Sessions
A session is a bounded work block — a start, some output, and an end. Sessions give structure to developer work so that stopping and restarting has a reliable handoff point.
Resume
Open the project in the browser or run pm resume.
Work
Complete tasks, resolve issues, link commits, and add notes.
End Session
Review what changed, update memory, and save the handoff.
Return
See current status and next action immediately — no reconstruction.
Shared sessions: The web app and CLI operate against the same backend session. Tasks completed in the terminal appear in the web End Session review. There is one consistent project history regardless of which interface you use.
Multiple projects: You can have sessions active across multiple projects. The CLI tracks a current project, which can be set by linking your repository directory to a project with pm project link.
Tasks
Tasks are the concrete work items attached to a project. They keep the immediate work list clear and can be linked to commits and project context.
Priority
Tasks carry a Low, Medium, or High priority. Today's Focus orders scheduled tasks by due date and priority, then considers unscheduled tasks by priority and age.
Snooze
Snooze a task until a specific date or mark it as "Someday" to remove it from the active board without deleting it.
Commit linking
When completing a task from the CLI with pm task done <id>, you are offered the option to link the relevant Git commit.
CLI — task workflow
$ pm task list
$ pm task add "Write API tests" --priority high
$ pm task done 14
$ pm done # interactive completion shortcut
Markdown import: Tasks can be bulk-created by uploading a Markdown file containing - [ ] item checklist syntax, or by pulling a Markdown file directly from a connected GitHub repository.
Issues
Issues are project-level blockers and known bugs. They can be linked directly as the Next Action and are considered by Today's Focus when no actionable task is available.
Open issues
Appear in the Memory tab alongside project context. Open issues remain available for direct linking and for the empty Next Action suggestion.
Resolving issues
Mark an issue resolved from the web workspace or with pm issue resolve <id> from the CLI. Resolved issues are archived and removed from the active Memory context.
CLI — issues
$ pm issue list
$ pm issue add "Stripe webhook not confirming renewal"
$ pm issue resolve 7
Notes
Notes provide detailed, free-form documentation for a project. Use them to record architecture decisions in long form, document code patterns, capture meeting outcomes, or write any reference content that doesn't belong in a task.
Plain-text capture
Notes keep lightweight project reference text without requiring a rich-text editor or special formatting workflow.
Optional title
Titles are optional. A quick capture note can be just content — useful for fast context drops mid-session.
Quick capture
From the CLI: pm capture "message" creates a note instantly without prompts.
CLI — notes
$ pm capture "Don't forget to update the Stripe webhook URL after deploy"
$ pm note add "Architecture overview" --editor
$ pm note list
$ pm note search "webhook"
Decisions
The Decisions register is an Architecture Decision Log (ADL) built into every project workspace. It answers: why did we build it this way? — so reasoning stays with the project, not in someone's memory.
Decision fields
- Title: The decision in one line.
- Reason: The context and rationale behind it.
- Category: General, Technical, Architecture, Product, Business, Infrastructure, or Research.
- Date: When the decision was made.
Links to project items
Each decision can be linked to related tasks, issues, and sessions — connecting the reasoning to the specific work items and context that drove it.
In team workspaces, decisions can also be created directly as the outcome of a Discussion.
GitHub Integration
Connect a GitHub repository to a project to bring commit history, pull requests, and repository issues alongside the project context where they are most relevant.
Commit activity
Synced commits appear on the GitHub tab and in session reviews. Automatic commit and changed-file sync follows the connected repository's default branch.
Task to commit mapping
Link specific commits to completed tasks from the web workspace or using pm commit link from the CLI.
Markdown task import
Pull Markdown files directly from the connected repository and import - [ ] checklist items as project tasks.
Setup
GitHub integration is configured from the GitHub tab inside the project workspace. Repository connection and authorization are web-only. Once connected, the CLI inherits the repository context automatically via directory linking.
CLI — Official Terminal Client
The official CLI (pm) connects directly to the same backend as the web app. Tasks completed in the terminal appear in the web Session Review. Sessions ended via the web are reflected in the CLI. There is one shared project state.
Installation
pipx install projectmemory-cli
Core workflow
# Authenticate
$ pm login
# Link your directory to a project
$ pm project link "My App"
# Resume context
$ pm resume
# View your next action
$ pm next
# Add and complete tasks
$ pm task add "Fix OAuth callback"
$ pm done
# Capture a quick note
$ pm capture "update webhook URL after deploy"
# End session
$ pm session end
| Command group | Key commands | What it does |
|---|---|---|
| Auth | pm login / logout / whoami | Browser-based OAuth, secure token storage via OS Keyring |
| Projects | pm project list / create / link | List, create, and link local directories to remote projects |
| Sessions | pm resume / session end | Start or resume sessions, end with a shared factual review |
| Memory | pm memory show / update | View and update project context fields from the terminal |
| Tasks | pm task list / add / done | Manage tasks, complete with optional commit linking |
| Notes | pm capture / note add / list | Quick capture or full note creation with editor support |
| Issues | pm issue add / resolve / list | Report and resolve project-level blockers |
| Commits | pm commit link | Link Git commits to completed tasks |
| Diagnostics | pm doctor | Read-only health check for config, auth, session, and network |
Security: Tokens are stored in the OS Keyring. The PROJECTMEMORY_TOKEN environment variable can be used to override stored credentials. Tokens can be revoked remotely via pm logout or from Account Settings in the web app.
Teams & Collaboration
Collaboration in Project Memory is project-based. The project owner invites collaborators into a specific project; shared projects do not count toward a collaborator's personal project allowance.
Shared Memory
All collaborators see the same Current Status, Next Action, Important Context, and Open Issues. There is one shared project state.
Roles
Owners invite members as Full Access or Contributor. Full Access can update shared Memory and project content; Contributors create work and edit the items they own. Free includes limited collaboration, with higher capacities on paid plans.
Task Assignment
Assign tasks to specific collaborators. Completion is attributed so the session review shows who closed what.
Discussions
Start threaded discussions from supported project items. A resolved discussion can create a Task, Issue, or Decision while preserving the conversation and outcome.
Shared Sessions
Each collaborator can start and end sessions independently. All sessions are logged against the shared project history.
Handoffs
End-session summaries are visible in the shared activity timeline, giving the next person a factual record of what changed.
AI Assists
Project Memory is not an AI wrapper. AI Assists are optional, review-first tools for Smart Resume, Smart Handoff, and discussion outcomes. They produce drafts that you review before anything changes.
AI Smart Handoff
At session end, draft a concise handoff summary drawn from completed tasks, resolved issues, linked commits, and changed files. The draft is shown to you before anything is written to Project Memory.
AI Smart Resume
When resuming a project with significant changes since the last session, optionally generate a suggested resume brief from the latest Memory fields and session history.
Discussion Outcome
Draft a concise resolution from the discussion, replies, linked work, and relevant Project Memory, then review it before resolving.
You stay in control
AI suggestions are drafts only. Project Memory never silently rewrites your memory, decisions, or handoffs. Each AI Assist consumes one Assist from your monthly allocation and requires explicit confirmation before generating.
Founding Pro and Pro include 10 AI Assists per month, Team includes 100, and Scale includes 300. Free does not include AI Assists. Purchased top-ups are available to Team and Scale accounts.
Key Concepts
A reference for terms used throughout the product.
- Project Memory
- The structured context fields (Current Status, Next Action, Important Context, Open Issues) attached to a project. Updated manually or during session review.
- Session
- A bounded block of work with a defined start and end. Sessions produce a shared review of what changed, visible in both the web app and CLI.
- Next Action
- The single immediate move in a project. Set manually or linked to a task or issue. When empty, Today's Focus can offer an open task or issue for the user to accept.
- Directory linking
- Running
pm project linkin a Git repository maps that directory to a Project Memory project. Subsequent CLI commands in that directory automatically use the linked project. - AI Assist
- A single use of the AI draft feature. Requires explicit confirmation before generation and does not alter Project Memory unless you approve and publish the draft.
- Owned project
- A project created by you, counting toward your plan's project limit. Shared projects you join as a collaborator do not count toward your personal limit.
- Discussion
- A threaded conversation linked to supported project context. Resolution may preserve an outcome as a Decision, Task, or Issue.
The web app and CLI share the same backend session and project history.
Built for development teams
One shared memory for every project your team touches.
Project Memory gives every collaborator the same view — current status, next action, decisions, open issues, session handoffs, and GitHub activity — so anyone can resume without asking what changed.
Start free. Invite your team when you're ready.
Every collaborator sees the same status, next action, and decisions.
End a session and leave a clear record of what changed.
Commits, PRs, and issues stay near the work your team is doing.
LaunchFlow SaaS
Active 3 collaboratorsLast updated just now · Memory updated just now · GitHub connected
Project Memory
The current state of the project, kept close to the work.
Next Action
Finish billing webhook tests
Linked to task: verify renewal and cancellation states.
Current Status
Auth is stable. Billing flow needs final webhook testing.
Checkout works. Subscription state copy is being reviewed.
Open Issues
- Stripe webhook not confirming plan update
- GitHub sync sometimes delays after install
Important Context
Free includes limited collaboration. Pro adds monthly AI Assists.
Today's Focus
Finish webhook tests, then save the session summary.
Memory Health
GitHub Activity
Connected3 commits
PR #12: Repository sync improvements
Issue #8: Callback redirect fails on some setups
Team Handoff
Maya ended session: webhook tests passed, PR merged. Rooh picking up billing state copy next.
The problem
Coding moves fast. Context disappears faster.
Every project leaves a trail of commits, tasks, issues, decisions, and half-remembered conversations. Project Memory turns that trail into a clear place to continue.
Where did we stop?
The project made sense yesterday. Today it needs reconstruction.
Why did we decide that?
Decisions get separated from issues, tasks, and code.
What comes next?
A clear next action beats another cold-start session.
Project Memory
One place for the state of your project.
Not a generic task board. Not a loose document. A focused workspace for what needs to be remembered when development resumes.
Current Status
Where the project stands
Capture the present state so nobody has to infer it from old activity.
Next Action
The next useful move
Write it manually or link it to a task or issue.
Important Context
The why behind the work
Keep constraints, reminders, assumptions, and decisions visible.
Open Issues
What still needs attention
Track blockers beside the memory they affect.
Sessions
Work in sessions. Return with context.
A session turns scattered progress into a clean review: completed tasks, resolved issues, commits, files changed, and anything else worth remembering.
Start or resume
Open the project in web or run pm resume.
Do the work
Complete tasks, resolve issues, add notes, and link commits.
End session
Review what changed and add optional notes.
Return later
See the current state and next action immediately.
Collaboration
Shared context for every project.
Invite collaborators into a specific project, give them the right role, and keep work, discussions, decisions, and handoffs attached to the same memory.
Shared Project Memory
Everyone sees the same current status, next action, and context.
Project Roles
Control who can manage, contribute, or view project work.
Task Assignment
Assign work and preserve completion attribution.
Discussions
Turn project conversations into decisions, tasks, or issues.
Shared Sessions
Each collaborator can save session context against the project.
GitHub Context
Repository activity stays visible beside project decisions.
Discussions
Turn conversations into project memory.
Start a discussion from a task, issue, decision, Project Memory field, or GitHub issue. Capture the outcome as a decision, task, issue, or memory update.
Issue
Webhook callback fails on renewal
Discussion
Should we retry status sync or wait for webhook confirmation?
AI assists
AI where context matters most.
Project Memory is not an AI wrapper. AI assists are optional, human-controlled drafts for the moments where context is hardest to reconstruct.
AI Smart Handoff
Draft a concise end-session summary from completed work, resolved issues, commits, and changed files.
AI Smart Resume
Generate a suggested resume brief from the latest Project Memory and session history.
You stay in control.
AI suggestions are drafts only. Project Memory never silently rewrites your memory, decisions, or handoffs.
Developer workflow
Works where developers work.
Use the web workspace for planning and collaboration, the official CLI when you are in the terminal, and GitHub integration to keep code activity connected.
$ pm resume LaunchFlow
Project: LaunchFlow SaaS
Current Status: Auth stable. Billing webhook needs testing.
Next Action: Finish billing webhook tests.
Since last session: 2 tasks completed, 3 commits, 1 issue resolved.
Pricing
Choose the amount of context and collaboration you need.
Start free. Upgrade when you need more owned projects, more collaborators per project, or AI assists.
Get Pro for $4/month or $40/year.
Lock this rate while your subscription remains continuously active. Founding Pro includes unlimited owned projects, collaboration across up to 5 projects, 3 collaborators per project, and 10 AI Assists/month.
Free
For getting one focused workspace into motion.
$0
Forever
- ✓2 owned projects
- ✓2 collaborative projects, 1 collaborator/project
- ✓Project Memory workflow
- ✓Tasks, issues, notes, decisions, sessions
- ✓GitHub integration and official CLI
Pro
For developers and small teams with multiple projects.
$8/month
$80/year annually
- ✓Everything in Free
- ✓Unlimited owned projects
- ✓Collaborate across up to 5 projects
- ✓Up to 3 collaborators per project
- ✓10 AI Assists/month
- ✓Roles, discussions, assignments, and history
Team
For teams that want collaboration plus AI-assisted handoffs.
$19/month
Monthly during AI Early Access
- ✓Everything in Pro
- ✓Collaborate across up to 20 projects
- ✓Up to 10 collaborators per project
- ✓100 AI Assists/month
- ✓AI Smart Handoff and AI Smart Resume
Scale
For larger project teams with heavier AI usage.
$49/month
Monthly
- ✓Everything in Team
- ✓Unlimited collaborative projects
- ✓Up to 30 collaborators per project
- ✓300 AI Assists/month
- ✓Contact us if you need more than 30 collaborators
Project-based collaboration. Your plan defines how many owned projects can use collaboration and how many collaborators can join each project.
Plan comparison
| Feature | Free | Pro | Team | Scale |
|---|---|---|---|---|
| Owned projects | 2 | Unlimited | Unlimited | Unlimited |
| Collaborative projects | 2 | 5 | 20 | Unlimited |
| Collaborators per project | 1 | 3 | 10 | 30 |
| Project Memory | Included | Included | Included | Included |
| Tasks, issues, notes, decisions, sessions | Included | Included | Included | Included |
| GitHub integration | Included | Included | Included | Included |
| Official CLI | Included | Included | Included | Included |
| Team roles and discussions | - | Included | Included | Included |
| AI Smart Handoff and Resume | - | - | Included | Included |
| AI Assists | 0 | 10/month | 100/month | 300/month |
FAQ
Clear answers for teams choosing a project memory system.
What is Project Memory?
Project Memory is a workspace for preserving project context: current status, next action, decisions, issues, sessions, GitHub activity, and team handoffs.
Is this a project management tool?
It includes tasks and issues, but the center of the product is context continuity - helping you and your team resume real work faster.
How are collaborators counted?
Collaboration is project-based. Your plan determines how many of your projects can use collaboration and how many collaborators can join each project.
Do collaborators need a paid plan?
No. The project owner's plan provides collaboration access. Shared projects do not count toward a collaborator's personal owned-project allowance.
What are AI Assists?
AI Assists are optional help for drafting handoffs and resume summaries. They do not automatically change your Project Memory.
Can I use Project Memory without AI?
Yes. Free and Pro include the full non-AI Project Memory workflow, GitHub integration, CLI, sessions, discussions, and collaboration features according to plan.
Does it work with GitHub and the terminal?
Yes. GitHub keeps code activity close to your project context, and the official CLI lets you resume, update tasks, capture notes, and end sessions from your terminal.
Start with one project
Stop reconstructing project context.
Give yourself and your team a reliable place to remember where the project stands, what changed, and what happens next.