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

Implement session/fork in v2

Open
  • Is something wrong?
#166 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
api

Research direction

Start by comparing the v2 builder in src/protocols/acp/v2.rs with the existing v1 session/fork path. Trace how v2 advertises capabilities and how the kit.subagent.parent_id and parent_name _meta values are handled; done means session/fork is supported and advertised with matching metadata behavior.

Written by the indexing model from the issue text.

Description

enhancement

v1 handles session/fork; the v2 builder in src/protocols/acp/v2.rs has no handler and does not advertise session.fork. Port the v1 fork path, including the kit.subagent.parent_id and parent_name _meta handling.

Part of #146.

Dominant language
Rust
Stars
42
Forks
5
Avg merge
5h 6m
Merged PRs (30d)
119

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 speakeasy-api/kit

All issues in speakeasy-api/kit

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.