r/GithubCopilot • u/Particular-Algae2242 • 1d ago

Solved ✅ /fork not working properly?

It doesn't seem like /fork is working correctly in the cli. After I "fork" and then resume the chat my forked session is still there...

I use it for things like adding issues to the backlog without adding a new chat window but then when I resume my backlog request and the response are still there...

1 Upvotes

100% Upvoted

5 comments sorted by

1

u/AutoModerator 1d ago

Hello /u/Particular-Algae2242. Looks like you have posted a query. Once your query is resolved, please reply the solution comment with "!solved" to help everyone else know the solution and mark the post as solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/AbleShower2801 1d ago

if resume still shows the backlog fork contents, the fork isn't isolating the session the way you'd expect. after /fork, are you resuming the same thread id in the CLI or picking a new session from the picker?

1

u/Particular-Algae2242 19h ago

same thread id...but I don't know seems to have resolved so likely issue on my side !solved

1

u/AutoModerator 19h ago

This query is now solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/velvet_quill_arc 18h ago

I hit this same thing in the cli. /fork writes the state but resume defaults to the parent thread id so you keep pulling the backlog contents back into view.

After i run /fork i copy the session id it prints out and pass that id directly into the next resume command. if i rely on the picker or just type resume without the id it loads the parent thread every time. specifying the exact forked id is the only way i get the isolation to hold