Skip to content

[FEATURE] Add task resumption support to submit commands #8

@claude

Description

@claude

Summary

Add support for resuming existing tasks/contexts in the tasks submit and tasks submit-streaming commands to enable debugging of ongoing conversations and input-required scenarios.

Background

Based on analysis of the A2A ADK implementation (see inference-gateway/adk#49), the A2A protocol properly supports:

  • Context ID maintenance across task sessions
  • Task ID resumption for input-required scenarios
  • Both streaming and async polling modes with context preservation

However, the a2a-debugger currently lacks the ability to resume existing tasks/contexts, making it difficult to debug scenarios where:

  1. A task transitions to input-required state
  2. An agent needs additional context to continue processing
  3. Debugging multi-turn conversations that span multiple interactions

Feature Request

Enhance the existing tasks submit and tasks submit-streaming commands with new optional parameters:

New Parameters

  • --task-id <task-id> - Resume an existing task by providing its Task ID
  • --context-id <context-id> - Continue within an existing context (for new tasks in the same conversation)

Usage Examples

# Resume a task that's in input-required state
a2a-debugger tasks submit --url http://agent:8080/a2a --task-id "task-123" --message "Here's the additional information you requested"

# Submit a new task within an existing context
a2a-debugger tasks submit --url http://agent:8080/a2a --context-id "ctx-456" --message "Follow up question"

# Resume with streaming
a2a-debugger tasks submit-streaming --url http://agent:8080/a2a --task-id "task-123" --message "Continue processing"

Implementation Details

The commands should:

  1. Include taskId and/or contextId fields in the A2A message payload when provided
  2. Handle task resumption responses appropriately
  3. Maintain backward compatibility with existing usage
  4. Support both streaming and non-streaming modes

Acceptance Criteria

  • tasks submit command accepts optional --task-id and --context-id parameters
  • tasks submit-streaming command accepts optional --task-id and --context-id parameters
  • Parameters are properly included in A2A message payload
  • Backward compatibility maintained for existing usage
  • Error handling for invalid Task IDs or Context IDs
  • Documentation updated with usage examples

Use Cases

  1. Input-Required Debugging: Resume a task that paused for additional input
  2. Multi-Turn Conversations: Continue debugging a conversation across multiple command invocations
  3. Context Preservation: Test how agents maintain context across task boundaries
  4. Task State Transitions: Debug task lifecycle and state management

This enhancement would make the a2a-debugger more powerful for testing complex agent interactions and debugging real-world A2A protocol scenarios.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions