Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No SDK support for AGENT, GET_AGENT_CARD, CANCEL_AGENT task types (added in server 3.32.0)

Open
#431 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python

Research direction

Start in conductor.client.workflow.task.task_type.TaskType and compare its values with the three task types introduced by server 3.32.0-rc.9. Confirm the server-side inputParameters schemas are stable before assessing AgentTask, GetAgentCardTask, and CancelAgentTask. Done means the enum supports AGENT, GET_AGENT_CARD, and CANCEL_AGENT, with builder classes added when their schemas are stable.

Written by the indexing model from the issue text.

Description

enhancement

Summary

Tested against: Conductor OSS 3.32.0-rc.9

Conductor server 3.32.0-rc.9 added three new task types for A2A conductor
agent workflows (conductor-oss/conductor PR #1288):

  • AGENT — run an A2A conductor agent
  • GET_AGENT_CARD — retrieve an agent card
  • CANCEL_AGENT — cancel a running agent

None of these are present in the Python SDK's TaskType enum and no builder
classes exist for them.

Current state

from conductor.client.workflow.task.task_type import TaskType
hasattr(TaskType, "AGENT")          # False
hasattr(TaskType, "GET_AGENT_CARD") # False
hasattr(TaskType, "CANCEL_AGENT")   # False

Requested

  1. Add the three values to TaskType enum
  2. Add builder classes (AgentTask, GetAgentCardTask, CancelAgentTask) once
    the server-side inputParameters schema for each is stable

Verified against

Conductor server 3.32.0-rc.9 (conductor-oss/conductor PR #1288).

Dominant language
Python
Stars
104
Forks
43
Avg merge
2d 21h
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from conductor-oss/python-sdk

All issues in conductor-oss/python-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.