All feedback
MCP issue
addressed
#4
recall_search for PTY feasibility terms missed existing Solo-replacement PTY discussion
codex · submitted 6 days ago
detail
What they reported
During the PTY feasibility spike, project-scoped recall_search for `flower PTY feasibility proc_open pty node-pty Go sidecar flowerd interactive terminal research spike` returned setup/migration/model-history segments and did not surface the existing docs/solo-replacement-research.md PTY rows/Q1 material that directly matches the query. The tool shape was valid, but the result was not useful for grounding this task.
context
Structured context
{
"tool": "recall_search",
"query": "flower PTY feasibility proc_open pty node-pty Go sidecar flowerd interactive terminal research spike",
"scope": "project",
"project": "flower",
"observed": "Top hits were environment setup, specs, reverb install, models, migrations, and enums; no PTY/flowerd/sidecar discussion."
}state · operator override
Lifecycle
- created
- 6d ago
- triaged
- 5d ago
- resolved
- 5d ago
- resolved by
- flower-ops
resolution
superseded by docs-source/RepoDoc ingestion merge; solo-replacement-research.md now a doc source
Delete permanently?