TaskType enum missing AGENT, GET_AGENT_CARD, CANCEL_AGENT, PULL_WORKFLOW_MESSAGES
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api
Research direction
Open src/open-api/types.ts and inspect the TaskType enum, which currently ends at LIST_MCP_TOOLS. Add the four server values listed in the issue, then verify the TypeScript SDK builds and that all four names can be referenced without raw strings.
Written by the indexing model from the issue text.
Description
Summary
Four task types added to the Conductor server in 3.32.0-rc.9 (conductor-oss/conductor PR #1288)
are absent from the TaskType enum in src/open-api/types.ts. Users cannot reference
these types via the SDK without using raw strings.
Server baseline
Conductor 3.32.0-rc.9
Missing values
Server TaskType.java has:
PULL_WORKFLOW_MESSAGES,
AGENT,
GET_AGENT_CARD,
CANCEL_AGENT;
All four are absent from the SDK TaskType enum.
Evidence
Static: TaskType enum in types.ts ends at LIST_MCP_TOOLS. All four values absent.
Live (2026-07-16): A raw task with "type": "AGENT" was registered against
Conductor OSS 3.32.0-rc.9. Server accepted the definition — the gap is SDK-only.
Proposed fix
Add to TaskType enum in src/open-api/types.ts:
PULL_WORKFLOW_MESSAGES = "PULL_WORKFLOW_MESSAGES",
AGENT = "AGENT",
GET_AGENT_CARD = "GET_AGENT_CARD",
CANCEL_AGENT = "CANCEL_AGENT",
Builder functions for AGENT, GET_AGENT_CARD, and CANCEL_AGENT should follow once the
agent task API is stable.
Related
Discovered during systematic SDK audit against Conductor OSS 3.32.0-rc.9.
Server PR: conductor-oss/conductor#1288
Same gap in Java SDK (conductor-oss/java-sdk#135) and Python SDK (conductor-oss/python-sdk#431).
- Dominant language
- TypeScript
- Stars
- 58
- Forks
- 20
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 7
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from conductor-oss/javascript-sdk
-
bug documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
conductor-oss/javascript-sdk#173 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
conductor-oss/javascript-sdk#139 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 91/100
conductor-oss/javascript-sdk#138 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
conductor-oss/javascript-sdk#137 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
conductor-oss/javascript-sdk#136 ·
All issues in conductor-oss/javascript-sdk
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·