Summary
Task delegation is currently difficult to use, unreliable, and lacks visibility.
While delegation is a very powerful concept, the current workflow makes it hard to understand what delegated agents are doing and how their work relates to the main session.
Current Pain Points
1. Delegation Requires an Existing Conversation
Currently, to delegate work:
- A chat must already exist.
- The chat must generally contain at least one interaction.
- Delegation cannot easily be configured during task creation.
This creates unnecessary friction.
Expected Behavior
When creating a Kanban task:
New Task
Title: [________________]
Executor:
( ) Claude
( ) Codex
( ) Gemini
( ) Custom
Mode:
( ) Direct execution
( ) Delegated execution
The task should immediately start with the selected executor.
2. No Delegation from Task Creation
Today, users often need to:
- Create task.
- Open chat.
- Start conversation.
- Configure delegation.
- Launch delegated agent.
Instead, users should be able to:
Create Task
↓
Assign to Codex
↓
Run
in a single workflow.
3. No Visibility Into What The Delegated Agent Is Doing
When a delegation is running:
a banner may appear, but there is little visibility into:
- Current progress
- Commands executed
- Files modified
- Intermediate reasoning
- Task status
Expected Behavior
A delegated task should expose:
Task
└─ Delegation
├─ Status
├─ Logs
├─ Terminal
├─ Files Changed
└─ Final Result
4. No Dedicated Terminal for Delegated Agents
When Codex is working:
- No dedicated terminal view is visible.
- No clear activity stream exists.
- Users cannot monitor execution in real time.
Suggested Solution
Open automatically:
or
showing:
- Commands
- Output
- Progress
- Errors
5. Multiple Delegations Are Difficult To Follow
Example:
Task A delegated
Task B delegated
Only one banner may remain visible.
Users can lose track of:
- Which delegation belongs to which task.
- Which delegation is still running.
- Which one has completed.
Expected Behavior
A dedicated panel:
Delegations
● Codex #1 Running
● Codex #2 Running
✓ Codex #3 Completed
⚠ Codex #4 Failed
6. Continue an Existing Session Using Another CLI
A very valuable workflow would be:
Claude Session
↓
Continue with Codex
or
Codex Session
↓
Continue with Claude
The target CLI receives:
- Chat history
- Context
- Files
- Task objective
without starting from scratch.
Example
Claude
→ Analysis
Codex
→ Implementation
Claude
→ Review
Codex
→ Fixes
7. Claude as an Orchestrator
Another powerful use case:
Claude
├─ Delegate subtask #1 to Codex
├─ Delegate subtask #2 to Codex
├─ Delegate subtask #3 to Gemini
└─ Aggregate results
The orchestrator should:
- Dispatch micro-tasks.
- Track progress.
- Gather outputs.
- Present a consolidated result.
8. Missing Delegation Tracking
A delegated task should have:
Started
Running
Waiting
Completed
Failed
Cancelled
and display:
Provider
Model
Duration
Cost
Files Changed
Suggested New UI
Task
├─ Chat
├─ Terminal
├─ Schedule
├─ Delegations
│ ├─ Codex
│ ├─ Claude
│ └─ Gemini
└─ Activity
Benefits
- Easier delegation workflow.
- Better multi-agent orchestration.
- Better visibility into agent activity.
- Easier debugging.
- Better support for Codex and other providers.
- Reduced user confusion.
- More powerful autonomous workflows.
Priority
High
Use Case
As a user, I want to create, monitor, and manage delegated tasks directly from the Kanban workflow so that Claude can act as
Summary
Task delegation is currently difficult to use, unreliable, and lacks visibility.
While delegation is a very powerful concept, the current workflow makes it hard to understand what delegated agents are doing and how their work relates to the main session.
Current Pain Points
1. Delegation Requires an Existing Conversation
Currently, to delegate work:
This creates unnecessary friction.
Expected Behavior
When creating a Kanban task:
The task should immediately start with the selected executor.
2. No Delegation from Task Creation
Today, users often need to:
Instead, users should be able to:
in a single workflow.
3. No Visibility Into What The Delegated Agent Is Doing
When a delegation is running:
a banner may appear, but there is little visibility into:
Expected Behavior
A delegated task should expose:
4. No Dedicated Terminal for Delegated Agents
When Codex is working:
Suggested Solution
Open automatically:
or
showing:
5. Multiple Delegations Are Difficult To Follow
Example:
Only one banner may remain visible.
Users can lose track of:
Expected Behavior
A dedicated panel:
6. Continue an Existing Session Using Another CLI
A very valuable workflow would be:
or
The target CLI receives:
without starting from scratch.
Example
7. Claude as an Orchestrator
Another powerful use case:
The orchestrator should:
8. Missing Delegation Tracking
A delegated task should have:
and display:
Suggested New UI
Benefits
Priority
High
Use Case
As a user, I want to create, monitor, and manage delegated tasks directly from the Kanban workflow so that Claude can act as