Feature request: selective Discord session visibility in Agents sidebar

[velocitystar]

Summary

In Nerve’s Agents sidebar, session visibility currently depends on lineage rooted in agent:<id>:main plus resolvable parent relationships. In multi-agent Discord deployments, operators often need tighter control over what appears in the sidebar.

This can lead to either:

• desired Discord sessions not appearing, or
• noisy views when too many session types are visible.

Feature Request

Add an optional, config-driven selective visibility layer for sidebar sessions (allow/deny), with no behavior change unless explicitly enabled.

Why This Is Valuable

1. Cleaner operator UX in active multi-agent setups.
2. Better focus by surfacing only operationally relevant sessions.
3. Less cognitive load during live incident handling and agent supervision.
4. Maintains backward compatibility by keeping defaults unchanged.
5. Reduces pressure to alter gateway/session internals just for UI organization.

Desired Filtering Dimensions

• agent id (main, lucy, etc.)
• channel/provider (discord, telegram, webchat)
• session kind (main, subagent, cron, direct, channel)
• explicit session-key patterns

Example Config (Conceptual)

{
  "ui": {
    "agentsSidebar": {
      "sessionVisibility": {
        "enabled": true,
        "allow": {
          "agents": ["main", "lucy"],
          "channels": ["discord"],
          "kinds": ["main", "subagent", "direct", "channel"],
          "sessionKeyPatterns": ["agent:main:discord:*", "agent:lucy:*"]
        },
        "deny": {
          "sessionKeyPatterns": ["agent:*:cron:*:run:*"]
        }
      }
    }
  }
}

Backward Compatibility

• Feature disabled by default.
• Existing installations preserve current behavior unless opted in.

Related Context

• Recently opened spawn-reliability fix PR: fix(spawn): use sessions.create/send with compatibility fallback #223