# Reported issues for Palinode

Pod holds 19 of 23 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 [Palinode](/mcp/palinode).

## Most discussed

### parity: MCP inventory counts the deprecated `palinode_timeline` alias as its own capability

`palinode_timeline` is an unambiguous deprecated alias of `palinode_history` — declared in
`palinode/mcp.py`, deprecation-logged when called, and its output prefixed `[DEPRECATED]`.
But `palinode/core/parity.py` gives it its own `INVENTORY_BACKLOG` row (line 661) alongside
`palinode_history` (line 654), so the inventory guard counts a single capability twice.

PR #89 established the rule for the CLI surface while adding the `dream` alias: **an alias is
not a capability.** The same object registe

[Read the thread](https://github.com/phasespace-labs/palinode/issues/99) · 2026-08-10 · closed · 4 comments

### Ambient context search: automatic project-aware retrieval (ADR-008)

## Problem

With many memory files across multiple projects, search results from unrelated projects drown out relevant ones. A search for "ADR-004" from a palinode working directory returns results from other projects instead of the palinode-specific memory.

## Solution

Automatic ambient context boost. When searching from a project directory, memories tagged with matching project entities get a score boost after hybrid search fusion. Not a filter — a lens. Cross-project results still appear if

[Read the thread](https://github.com/phasespace-labs/palinode/issues/28) · 2026-04-12 · closed · 4 comments

### Multi-platform MCP and integration docs (Claude Code, Cursor, Zed, VS Code)

## Problem

Installing the Palinode MCP server varies by IDE and transport (stdio vs Streamable HTTP vs remote). The current docs cover Claude Code but lack clear setup instructions for other editors and agent integrations.

## Proposed solution

Create or expand `docs/INSTALL-CLAUDE-CODE.md` into a comprehensive multi-platform guide covering:

| Platform | Transport | Config location |
|----------|-----------|----------------|
| Claude Code | stdio or HTTP | `~/.claude/settings.json` |
| Cursor

[Read the thread](https://github.com/phasespace-labs/palinode/issues/24) · 2026-04-09 · closed · 4 comments

### OpenClaw plugin manifest rejects two documented config options

**If you'd like to take this, please comment here first and wait to be assigned before opening a
PR.** Two contributors landed on the same issue once because we had no such line; that was our
fault, and this is the fix.

`plugin/openclaw.plugin.json` declares its `configSchema` with `"additionalProperties": false` and
exactly five properties:

```
palinodeApiUrl  palinodeDir  autoCapture  autoRecall  promptsDir
```

`plugin/INSTALL.md` documents **seven**. The two missing ones are:

| Option | D

[Read the thread](https://github.com/phasespace-labs/palinode/issues/144) · 2026-08-17 · open · 3 comments

### Reindex runs on the event loop and freezes every other API endpoint

**If you'd like to take this, please comment here first and wait to be assigned before opening a
PR.** Two contributors landed on the same issue once because we had no such line; that was our
fault, and this is the fix.

`POST /reindex` is declared `async def`, but everything it does is synchronous. So it occupies the
event loop for the entire reindex, and every other endpoint — `/search`, `/health`, `/save`, and
every MCP tool that proxies through the API — waits for it to finish.

**Where it i

[Read the thread](https://github.com/phasespace-labs/palinode/issues/142) · 2026-08-17 · closed · 3 comments

### `palinode_save`'s MCP tool schema exceeds some clients' size caps and gets silently dropped

`palinode_save`'s MCP schema is ~4.8 KB. At least one MCP client caps tool schemas at 4,096 bytes and, on exceeding the cap, replaces the schema with an **empty object** rather than truncating or erroring — the tool still appears in the model's tool list, but with no parameter contract, so the model is invited to call a write tool blind.

Task: get the schema under 4 KB without losing the contract. The bulk is description text; candidates include tightening the per-field descriptions, moving wor

[Read the thread](https://github.com/phasespace-labs/palinode/issues/72) · 2026-08-03 · closed · 3 comments

### Migrate plugin from before_agent_start to before_prompt_build

before_prompt_build for new work. ~20 line change in plugin/index.ts.

[Read the thread](https://github.com/phasespace-labs/palinode/issues/2) · 2026-03-31 · closed · 3 comments

### feat(save): report created, resaved, disambiguated, or replaced outcome

> **Reserved for @Karunasagar12 until 2026-08-30.** It is assigned to me only as a tracker proxy so
> it doesn't read as free — it isn't mine and I'm not working on it. @Karunasagar12, comment here
> and I'll record your ownership; I'll switch the assignee to you if GitHub permits it, and
> otherwise keep the proxy in place. If that date passes with no reply, I'll drop the placeholder
> and it opens to anyone.

A save that replaces an existing memory returns a receipt identical to one that creat

[Read the thread](https://github.com/phasespace-labs/palinode/issues/147) · 2026-08-23 · open · 2 comments

## Most recent

### server.json: the MCP registry _meta block still points at the v0.13.0 release

`server.json` is the manifest published to the Official MCP Registry. Three of its version fields are current, and one block is not:

| Line | Field | Value |
|---|---|---|
| 11 | `version` | `0.14.0` ✅ |
| 17 | stdio package `version` | `0.14.0` ✅ |
| 68 | streamable-http package `version` | `0.14.0` ✅ |
| **130** | `_meta…publisher-provided.release` | **`v0.13.0`** ❌ |
| **131** | `_meta…publisher-provided.release_notes_url` | **`…/releases/tag/v0.13.0`** ❌ |

The manifest advertises 0.14.0 wh

[Read the thread](https://github.com/phasespace-labs/palinode/issues/163) · 2026-08-29 · closed · 1 comment

### search: re-evaluate MCP/API thresholds against the pinned abstention sweep

The standalone abstention evaluation (`bench.abstention`, added in #151) measured the per-arm relevance floor across three seeded corpora — 26 no-answer queries and 20 answer-present controls per seed — against the real embedder, SQLite-vec, FTS5, and ranking pipeline.

| threshold | no-answer queries returning a hit | exact controls | paraphrase controls |
|---:|---:|---:|---:|
| 0.40 | 62/78 | 30/30 | 25/30 |
| **0.45** | **25/78** | **30/30** | **25/30** |
| 0.50 | 8/78 | 30/30 | 23/30 |
| 0.

[Read the thread](https://github.com/phasespace-labs/palinode/issues/154) · 2026-08-28 · open · 0 comments

### Trigger endpoints return a generic 500 when the embedder is unavailable

**If you'd like to take this, please comment here first and wait to be assigned before opening a
PR.** Two contributors landed on the same issue yesterday because we had no such line and no
assignment; that was our fault, and this is the fix.

When the embedding backend is down, the same failure produces different answers depending on which
endpoint you hit.

`POST /search` and its neighbours return **503** with a message naming the backend, the model, and a
`palinode doctor` recovery hint — `pa

[Read the thread](https://github.com/phasespace-labs/palinode/issues/137) · 2026-08-15 · closed · 2 comments

### parity: API inventory counts the deprecated /timeline alias as its own capability

`GET /timeline/{file_path}` is deprecated in favour of `GET /history/{file_path}?detail=full` —
the handler logs exactly that (`palinode/api/routers/git_history.py`), and the history route's
own docstring describes itself as "formerly the /timeline endpoint". But
`INVENTORY_BACKLOG["api"]` in `palinode/core/parity.py` still lists the two as separate rows, so
the parity inventory counts one capability twice.

This is the same defect that was fixed for the MCP surface and then the CLI surface. **T

[Read the thread](https://github.com/phasespace-labs/palinode/issues/122) · 2026-08-13 · closed · 2 comments

### `palinode migrate`: support bullet-list memory exports (mem0 and similar)

`palinode migrate openclaw` imports structured section-based exports cleanly. Several memory tools
(mem0 among them) instead export a **flat date-bulleted list** — hundreds of one-line memories
with no section structure — which the importer cannot parse.

## What already exists, so you do not think you are duplicating it

`palinode/migration/` contains `mem0_export.py`, `mem0_classify.py` and `mem0_generate.py`. That
pipeline pulls from a **live Qdrant instance** over HTTP and classifies with a 

[Read the thread](https://github.com/phasespace-labs/palinode/issues/75) · 2026-08-03 · closed · 2 comments

### Anthropic Connectors Directory submission (MCPB or hosted Remote MCP)

## Why pending

Anthropic's Connectors Directory submission path requires a compatible distribution path such as a Desktop Extension (MCPB) bundle or a hosted Remote MCP server. Palinode is local-first (stdio plus local HTTP), and neither distribution path has been selected and shipped yet.

The earlier v0.8.7 / #61 prerequisite is obsolete; #61 shipped independently and does not deliver the bundle or hosted service needed here.

## Readiness already in place

- ✓ All 30 MCP tools in v0.9.8 carr

[Read the thread](https://github.com/phasespace-labs/palinode/issues/62) · 2026-04-30 · open · 0 comments

### Add llms-install.md for agent-bootstrap (Ollama detection + venv-path discipline)

## Why
Cline preflight test on 2026-04-29 successfully installed Palinode using only the README, but hit two avoidable friction points that an `llms-install.md` would eliminate:
1. **No explicit Ollama-existing-or-not check.** The README assumes Ollama is configured. When testing on a clean dev machine, the agent had to discover for itself that Ollama needed installing and bge-m3 needed pulling. A typical reviewer might give up here.
2. **Service-startup pythonpath ambiguity.** Entry points (`pa

[Read the thread](https://github.com/phasespace-labs/palinode/issues/61) · 2026-04-30 · closed · 1 comment

### Docs: public integration guide for OpenClaw and Hermes-agent

## Problem

OpenClaw and Hermes-agent were mentioned in the broader multi-platform MCP docs issue, but they are not really the same problem as editor-side MCP client setup.

They need their own public-facing integration guidance.

## Scope

Track setup and usage docs for:
- OpenClaw integration
- Hermes / Hermes-agent integration

## Desired outcome

Public docs that explain:
- when to use these integrations vs plain MCP client setup
- installation/setup flow
- any transport or config difference

[Read the thread](https://github.com/phasespace-labs/palinode/issues/60) · 2026-04-30 · closed · 1 comment

### Ship templated systemd unit files and install docs for self-hosted deployments

## Problem

Palinode works well as a self-hosted service, but the deployment story still depends too much on hand-written local service files and tribal knowledge.

That makes fresh installs, rebuilds, and host migrations harder than they need to be.

## Proposed solution

Ship version-controlled deployment templates for the core services and document the installation flow clearly.

Initial scope:
- templated `palinode-api` unit
- templated `palinode-mcp` unit
- templated `palinode-watcher` unit

[Read the thread](https://github.com/phasespace-labs/palinode/issues/51) · 2026-04-27 · closed · 1 comment

### Directory submissions — MCP Registry, Smithery, mcp.so, Cline

## What

Submit Palinode to community MCP directories.

## Status — 2026-08-02

The current release is v0.9.8. The Official MCP Registry publication is complete and live as `io.github.phasespace-labs/palinode`; the remaining community-directory submissions are still pending.

## Submissions

- [x] **Official MCP Registry** (`registry.modelcontextprotocol.io`) — live as `io.github.phasespace-labs/palinode`
- [ ] **Smithery** (`smithery.ai`) — publish as `@phasespace-labs/palinode`
- [ ] **mcp.so*

[Read the thread](https://github.com/phasespace-labs/palinode/issues/35) · 2026-04-13 · open · 1 comment

### Anthropic Connectors Directory: submission prep

## Context

The Anthropic Connectors Directory is the curated marketplace inside Claude (claude.ai, Claude Desktop, Claude Code). Submitting requires a **remote MCP server** accessible from Anthropic's infrastructure via HTTPS.

**Submission form:** https://docs.google.com/forms/d/e/1FAIpQLSeafJF2NDI7oYx1r8o0ycivCSVLNq92Mpc1FPxMKSw1CzDkqA/viewform

## Blockers

### Must have
- [ ] **HTTPS endpoint** — Palinode runs plain HTTP on :6341. Need TLS termination (Caddy/nginx reverse proxy) or native T

[Read the thread](https://github.com/phasespace-labs/palinode/issues/29) · 2026-04-13 · closed · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/phasespace-labs/palinode/issues).