[FEATURE] Football Manager-Style News Inbox for Multi-Agent Claude Code Sessions

Resolved 💬 4 comments Opened Apr 9, 2026 by rlarjsdid Closed May 23, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

I run 5+ Claude Code agents in parallel daily (Max plan, researcher in South Korea — care robotics translational research center).
The #1 friction: I have to constantly switch between terminal tabs to check permission requests ("Allow once" / "Deny") and monitor progress. There's no unified view of what all agents are doing.
The more agents you run, the worse it gets. Every tab-switch breaks flow state. A dangerous rm -rf request looks identical to a safe cat command until you manually read it in the right terminal.
My daily workflow involves: cognitive therapy chatbot dev, clinical photo processing, paper review, lecture material creation, presentation review — all running concurrently via Claude Code.

Proposed Solution

A Football Manager-style "news inbox" — a single unified feed where:

All permission requests from running agents appear as news items (agent name, action requested, risk level, context)
Approve/deny directly from the feed — "Allow once" / "Always allow" / "Deny" — without switching tabs
Agent status overview bar — compact view of all running agents (working / waiting for permission / done / error)
MCP integration — Google Calendar, Drive, Slack notifications also appear in the same feed
Risk indicators — color-coded by danger level (safe=green, caution=yellow, dangerous=red)

The key technical requirement: Claude Code agents need to expose permission requests via a shared channel (IPC, local API, websocket) rather than only through individual terminal stdin/stdout.
I've built a working React prototype demonstrating this concept with real Google Calendar MCP data + simulated agent permission requests. Happy to share.

!Image

Alternative Solutions

Currently I have multiple terminal windows tiled on screen and manually scan each one for permission prompts. I also tried using tmux with split panes, but it doesn't solve the core problem — there's no way to see a prioritized, unified queue of pending permission requests across agents.
Some users run agents with --dangerously-skip-permissions to avoid this friction entirely, but that defeats the purpose of the safety system.

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

I start my workday with 5 Claude Code agents already running: chatbot dev, clinical photo processing, paper review, lecture material creation, and slide review
Instead of checking 5 terminal tabs, I open a single "News Inbox" view
I see 8 pending items — 3 permission requests (highlighted by risk level), 2 agent progress updates, 3 calendar notifications from MCP
Agent "Chatbot Dev" requests: Bash: python -c "SUS scoring verification" — risk: LOW (green). I click "Allow once"
Agent "Photo Processing" requests: rm -rf /data/temp_cache/ — risk: HIGH (red). I review context and click "Deny"
I process all 8 items in under 2 minutes without switching a single terminal tab
This saves me ~30 minutes daily of context-switching overhead

Additional Context

Visual inspiration: Football Manager's news inbox — a single feed of categorized news items (transfers, injuries, board decisions) that you process one by one.
Prototype: I built a working React prototype combining real Google Calendar MCP data with simulated agent permission requests in an FM-style inbox. Happy to share code or screenshots.
Key technical requirement: Claude Code agents need to expose their permission queue via a shared channel (IPC, local socket, or websocket) so external UIs can read pending requests and send approve/deny responses.
Related concern: Many power users run --dangerously-skip-permissions just to avoid tab-switching friction — a unified inbox would make the safety system usable at scale.

<img width="668" height="902" alt="Image" src="https://github.com/user-attachments/assets/316d7a63-ca4c-4bce-b515-8c9badbf2791" />
<img width="1051" height="998" alt="Image" src="https://github.com/user-attachments/assets/9fafab43-a78b-404c-951c-aa732566348b" />

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗