Repository navigation
thread tool: create new threads in a thread's parent channel - #53
Merged
frolic merged 1 commit intoSep 14, 2026
Merged
Conversation
Discord forbids nesting threads, so invoking the thread tool from inside a thread used to fail outright. Now the host channel resolves to the thread's parent channel, letting a threaded session hand off to a fresh root thread (frolic requested this for cross-site coordination)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Discord forbids nesting threads, so the
threadtool refused to run from inside a thread ("cannot create a thread inside a thread"). This resolves the host channel to the thread's parent channel instead, letting a threaded session hand off to a fresh root-level thread.Trigger: frolic asked for a new root thread while we were inside the roadbikeshoes thread; the harness blocked it, and the only path was a two-line framework fix.
startThreadnow pickschannel.parentIdwhen the session channelisThread()and uses that as the host (falls back to the old error only when the parent is missing or not text-based).