Project memory for teams and AI
Keep the decisions. Continue the project.
SPM keeps approved decisions, open work and source evidence together, so the next person or agent can pick up where the project stands.
14-day Core trial · No card required
Your AI provider bills model usage separately. See pricing
Works with Codex, Claude Code, Cursor and OpenClaw.
Find your integration
Current decision
Retries must not create a second charge.
Approved by the project owner
Source: release requirements · 12 May
Test evidence is still missing
A newer suggestion to skip the test has not been approved.
The next agent receives
- The approved requirement
- The test still needing evidence
- The source behind the decision
Why does this decision still apply?
The approved requirement remains current. A later proposal is working context until an authorized decision changes it. Missing test evidence stays open and travels with the handoff.
An illustrative project view separates an approved decision, an unapproved suggestion and missing evidence before a handoff.
Product demo · about 3 minutes
One project. Different people. The right context for each.
Follow a billing change from engineering to release, partner review and support. See what each participant receives and what stays private.
This demonstration uses illustrative project data.
Read the video transcript
SPM is durable, shareable and governed project memory for AI agents. It keeps project knowledge outside the chat window and turns it into smart memory packs scoped by audience, weighted by time and authority, linked to source evidence, and auditable from creation to sharing.
In Luna Billing, an engineering lead gives one assigned cross-functional engineering request: fix billing webhook retries, prepare a partner handoff, and give support a customer-safe brief. This task assignment touches code, release risk, external collaboration, privacy and customer communication.
The same project thread can involve a product owner, coding agent, partner reviewer, and support lead. SPM keeps one shared project memory, but records who said what, when it was said, and which audience is allowed to receive it.
SPM separates that multi-audience project state into governed context areas. Backend gets implementation truth. Release gets risk and required tests. The partner gets integration facts. Support gets approved customer language.
The backend agent receives original billing constraints, current retry failures, implementation notes, and the required idempotency tests. It remembers the project facts it needs without receiving pricing, partner negotiation notes, or internal roadmap.
The release agent sees the part flat memory misses. A coding agent proposed a shortcut today. But the original safety rule was set by the security owner. SPM does not let the latest low-authority note become project truth.
The agent can still move. It can patch safe code, but release needs evidence: tests, policy checks, or explicit approval if the original safety rule is changed.
The external partner receives a context pack with endpoint changes, retry semantics, and an integration checklist. This is governed sharing: pricing, roadmap, internal security notes, and PII are outside the boundary.
Support receives a brief from the same project truth: what changed, customer impact, current status, and approved wording. No code internals, no private policy notes.
Every view leaves a verifiable record: boundary hash, pack hash, source, expiry, revoke controls, and the reason a memory was trusted, limited or sent for review.
SPM does not replace coding agents. It gives developers, agent teams and organizations durable project memory for cross-agent reuse: smart, scoped, shareable, governed and verifiable.
How it works
Stop rebuilding the project in every conversation.
- 01
Save a decision
Add a requirement, document or agent outcome. Keep who approved it and where it came from.
- 02
Keep changes in context
See which decisions still apply, which proposals need review and which work still needs evidence.
- 03
Continue with the right context
Give the next teammate or agent the current decision, open work and sources within their access permissions.
What travels with the work
More than remembering what was said.
An approved requirement, an agent suggestion and an unfinished test mean different things. SPM keeps those differences visible when work changes hands.
See how access and sharing work- Decisions with a source
- See who approved a decision and trace it back to the supporting material.
- Open work that stays open
- Missing evidence and unresolved changes remain visible to the next participant.
- A view for each audience
- Share the integration contract with a partner while keeping internal discussions outside their view.
Start with one real project
Keep the next handoff short.
Create a project, add a decision and connect your agent. Hosted Team starts at $49/month. Bring your own AI provider keys.
Need a private deployment? Talk to us