Reported issues for Postgram
Pod holds 8 of 8 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to Postgram.
Most discussed
Epic: memory grooming scope, age, and self-service
Context
Postgram session-context grooming currently requires a single client_id and uses a hard-coded 7-day age window. Operators need one-command grooming across clients, callers need configurable age, and agents should be able to dry-run/archive their own stale session context safely.
Approved design spec: docs/superpowers/specs/2026-06-07-memory-grooming-scope-age-self-design.md on branch codex/memory-grooming-scope-age-self.
Related follow-up: #47 tracks future agent-scoped LLM p
Read the thread · 2026-06-07 · closed · 7 comments
Enforce scoped durable-memory retrieval for promoted session context
Parent epic: #48
Context
The approved grooming spec requires promoted durable memories derived from session context to retain metadata.session_scope. Current search filtering treats session_context as scoped, but durable memories are globally visible even if metadata contains a source client scope. That would leak groomed durable memory across clients after admin all-client promotion.
End goal / deliverable
Update retrieval so durable memories with `metadata.session_scope.client_id
Read the thread · 2026-06-07 · closed · 1 comment
Add MCP groom_session_context self-grooming tool
Parent epic: #48
Depends on: Wave 1 service foundation and scoped retrieval safety.
Context
Agents use the MCP server heavily for session-context writes. They should be able to dry-run and archive their own stale session context through MCP without admin access. Promotion remains admin-only for this epic; future scoped promotion is tracked by #47.
End goal / deliverable
Add an MCP tool named groom_session_context with authenticated self-scope and modes:
dry_runarchive
Par
Read the thread · 2026-06-07 · closed · 1 comment
Add OAuth (DCR) so postgram works as a native remote connector without mcp-remote
Summary
postgram only does static Bearer auth today. That forces the mcp-remote stdio bridge on Claude Desktop and blocks adding postgram as a native remote connector on web/mobile. Add OAuth 2.0 so postgram can be added directly via Settings > Connectors across all surfaces.
Why
- Claude Desktop won't connect to remote servers from
claude_desktop_config.json— remote goes through the Connectors UI, which is OAuth/authless only, no arbitrary headers. So static Bearer = mcp-remote fore
Read the thread · 2026-06-11 · closed · 0 comments
MCP tool input validation rejects string-coerced arguments (limit, tags)
Summary
Some MCP clients/models send typed tool arguments as strings: numbers as "3", arrays as a JSON-encoded string "[\"a\",\"b\"]". The Zod input schemas reject these with -32602, so search and store fail even though the payload is semantically valid.
Impact
store (with tags) and search (with limit) break entirely when driven by a client that stringifies args. Same server works fine from clients that emit correct JSON types (e.g. Claude Code native). From the user's side
Read the thread · 2026-06-11 · closed · 0 comments
Add scoped session-context promotion for agent self-grooming
Context
Session-context grooming currently promotes only through the admin maintenance path. For the next grooming iteration we agreed that normal CLI/MCP self-grooming should start conservatively with scoped dry-run/archive, while LLM-assisted promotion stays admin-only.
We still want a future agent-facing promotion path, but it needs a more careful authority and audit design because promotion creates durable memory that future agents may trust.
Desired outcome
Design and implement an
Read the thread · 2026-06-07 · closed · 0 comments
Add first-class conversation history model for Talon integration
Summary
Extend Postgram with first-class conversation-history storage and retrieval primitives for Talon.
Why
Current Postgram is entity-centric. Talon needs message-level, thread-aware, role-aware retrieval plus compact state snapshots. This should not be squeezed into generic interaction entities.
Deliverables
conversationstablemessagestablestate_snapshotstablecontext_injectionstable- REST and MCP surface for message search, adjacency lookup, and latest sna
Read the thread · 2026-04-05 · open · 0 comments
Add owner/namespace field for multi-persona memory isolation
Problem
Postgram has no concept of ownership on entities. Every entity is globally visible. This blocks using postgram as a shared memory store for multiple Talon personas — a PM persona's memories are indistinguishable from a Dev persona's memories.
The visibility field (personal, work, shared) controls access scope but not ownership. There's no way to answer "show me only the PM's memories" or "what does the Dev persona know about this project?"
Use case
Talon's virtual team
Read the thread · 2026-03-31 · open · 0 comments
Most recent
The remaining reports are on the project's issue tracker.