microsoft / microsoft/conductor
req(acp) - workflow runtime support for ACP servers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 448
- Forks
- 65
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
I would like to see the introduction of an ACP based workflow runtime, so that conductor could leverage any runtime that supported an ACP interface and not only support new runtimes via code modifications. The ACP runtime could reference either an existing ACP server or a command to start a new sub-process as a server, example of leveraging copilot cli as a runtime.
workflow:
runtime:
provider:
name: acp
command: copilot
args:
- --acp
- --yolo
An existing ACP server could be referenced by a URL as part of the provider configuration
workflow:
runtime:
provider:
name: acp
url: https://host:port/
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.
Research direction
Start by tracing how workflow.runtime.provider is parsed and how existing runtimes are launched or addressed. Use the command, args, and URL examples in this issue to define the ACP runtime behavior; done should support both starting an ACP subprocess and connecting to an existing ACP server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100