self-API: spawn a fresh conversation - #204
Merged
Merged
Conversation
POST /v1/conversations creates a new conversation in a scope the caller can act in — the same operation the web UI's New Chat performs, now available to agents. The response carries the new conversation id and scope; guardrails match the surface route (scope membership, audit).
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
1 participant
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.
POST /v1/conversations {text, title?} — the agent can open a new session in its scope with a seed message it writes; no inherited transcript. Human-attended turns only.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.