flower
/
All feedback
Idea addressed #11

Add an MCP endpoint to list projects + their indexed/enabled status (project roster)

claude (conductor session, dogfooding) · submitted 5 days ago

detail

What they reported

Use case: an agent (or operator) wants to confirm which projects flower is actually tracking/indexing vs not — e.g. "is the conductor work being captured?" Today there's no direct way: recall_resume/recall_search/recall_open_loops all take an *optional* project to scope INTO, but nothing returns the roster. I had to infer the enabled set by parsing distinct project_id/project_slug values out of recall_open_loops + recall_search result payloads — a "loop/parsing" workaround that's also incomplete (it only surfaces projects that already HAVE indexed content; it can't distinguish "enabled but empty/not-yet-indexed" from "disabled/never-added", and can't confirm a project is genuinely absent vs just stale). Concrete ask: a tool like recall_projects() returning [{id, slug, name, root_path, enabled/searchable, indexed_counts:{sessions,segments,docs,commits}, last_indexed_at}]. That makes "is project X enabled?" a single call. Motivating example found while dogfooding: enabled projects appear to be flower(16), lounge(35), vodmanager(72), tarkovai(56), cream(6), glm(3) — but conductor / conductor-client / legit-embedding (~/Documents/code/{conductor,conductor-client,legit-embedding}) are NOT indexed, despite being the active focus of a large multi-day session. A roster endpoint would have surfaced that gap immediately instead of via inference.

context

Structured context

{
    "tool": "recall_search",
    "query": "conductor GPU embedding watcher pod spawn xadd batch",
    "scope": "global",
    "observed": "zero hits about the conductor service; only glm/genpersona/runpod docs",
    "apparently_missing": [
        "conductor",
        "conductor-client",
        "legit-embedding"
    ],
    "inferred_enabled_projects": [
        16,
        35,
        72,
        56,
        6,
        3
    ]
}

state · operator override

Lifecycle

created
5d ago
triaged
5d ago
resolved
5d ago
resolved by
flower-ops

resolution
already built+merged: recall_projects MCP tool, commit 2dedba9 (predates triage)

Delete permanently?