speakeasy-api / speakeasy-api/kit
Track upstream ACP session injection dependencies
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 40
- Forks
- 4
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 148
Description
Kit #24 lands ACP v2 session injection using pinned implementation branches while the protocol and SDK work is reviewed upstream.
Upstream work
- RFD: agentclientprotocol/agent-client-protocol#1261
- Protocol schema: agentclientprotocol/agent-client-protocol#2043
- Rust SDK response receipts: agentclientprotocol/rust-sdk#338
- Rust SDK injection support: agentclientprotocol/rust-sdk#339
- AgentKit ACP v2 foundation: danielkov/agentkit#12
- AgentKit injection implementation: danielkov/agentkit#13
Kit follow-up
- Replace the schema fork pin with an upstream release
- Replace the Rust SDK fork pin with upstream releases
- Replace the AgentKit fork patches with released crates
- Remove the temporary
[patch.crates-io]entries - Confirm all ACP and AgentKit packages resolve to one source identity
Kit implementation: speakeasy-api/kit#24
Current pins:
- Schema:
6e7e044f9464c4fd652d90699a09e9edc8b3bbad - Rust SDK:
2f039993d1d6ed8da35b38c31f54a7cbb7338c70 - AgentKit:
4299f31ec1455ea8ee4c46b4dce8e5bec4fdc597
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 with the ACP v2 implementation in Kit #24 and review the current dependency pins and temporary [patch.crates-io] entries. Track the listed upstream RFD, schema, Rust SDK, and AgentKit work, then confirm released crates resolve to one source identity and remove the temporary fork configuration when upstream releases are available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100