[GH-ISSUE #5883] Make metadata.chat_id available in custom pipeline #14159

New Issue

2026-04-19T20:36:46-05:00

GiteaMirror commented

2026-04-19 20:36:46 -05:00

Originally created by @weixu365 on GitHub (Oct 3, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/5883

Is your feature request related to a problem? Please describe.

I'm integrating open-webui with AWS Bedrock Agents using bedrock_agent_runtime.invoke_agent() in a custom pipeline. This method requires a sessionId parameter, as the Bedrock Agent manages the chat session.

I would like to use chat_id as the sessionId, but it's no longer available in the pipeline.pipe() method. The metadata field, where this information was previously stored, was removed 3 months ago in commit f462744.

Describe the solution you'd like

I propose restoring the metadata field from the payload at: https://github.com/open-webui/open-webui/blob/main/backend/open_webui/apps/openai/main.py#L383-L384

Describe alternatives you've considered

If reintroducing the metadata field could cause other issues, I suggest adding an environment variable, such as ENABLE_PIPELINE_METADATA. When this variable is not set or set to false, the default behavior (without metadata) would remain unchanged, while enabling it would send the field to custom pipelines

Additional context
None

Originally created by @weixu365 on GitHub (Oct 3, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/5883 **Is your feature request related to a problem? Please describe.** I'm integrating open-webui with AWS Bedrock Agents using bedrock_agent_runtime.invoke_agent() in a custom pipeline. This method requires a sessionId parameter, as the Bedrock Agent manages the chat session. I would like to use chat_id as the sessionId, but it's no longer available in the pipeline.pipe() method. The metadata field, where this information was previously stored, was removed 3 months ago in commit [f462744](https://github.com/open-webui/open-webui/commit/f462744#diff-84fe56d58871cf1f81dfe7cc81a247f1f61226cf2a152e95c8ee06c13d83f28fR360). **Describe the solution you'd like** I propose restoring the metadata field from the payload at: https://github.com/open-webui/open-webui/blob/main/backend/open_webui/apps/openai/main.py#L383-L384 **Describe alternatives you've considered** If reintroducing the metadata field could cause other issues, I suggest adding an environment variable, such as `ENABLE_PIPELINE_METADATA`. When this variable is not set or set to false, the default behavior (without metadata) would remain unchanged, while enabling it would send the field to custom pipelines **Additional context** None

GiteaMirror closed this issue

2026-04-19 20:36:46 -05:00

GiteaMirror commented

2026-04-19 20:36:47 -05:00

@weixu365 commented on GitHub (Oct 3, 2024):

Solved by adding to a custom field in body:

    async def inlet(self, body: dict, user: Optional[dict] = None) -> dict:
        body["pipeline_metadata"] = {"chat_id": body["chat_id"]}

        return body

@weixu365 commented on GitHub (Oct 3, 2024): Solved by adding to a custom field in body: ``` async def inlet(self, body: dict, user: Optional[dict] = None) -> dict: body["pipeline_metadata"] = {"chat_id": body["chat_id"]} return body ```

GiteaMirror commented

2026-04-19 20:36:48 -05:00

@codysandahl commented on GitHub (Jan 4, 2025):

For future people, if you need to get the extra metadata to the Pipelines server, I wrote a Pipe to package the info into the body and send it to Pipelines.
https://openwebui.com/f/codysandahl/pipeline_enriched_with_metadata

@codysandahl commented on GitHub (Jan 4, 2025): For future people, if you need to get the extra metadata to the Pipelines server, I wrote a Pipe to package the info into the body and send it to Pipelines. https://openwebui.com/f/codysandahl/pipeline_enriched_with_metadata

GiteaMirror referenced this issue

2026-04-19 22:54:18 -05:00

[GH-ISSUE #14159] issue: Web search via searxng leads to chromadb.errors.InvalidCollectionException: Collection web-search-xxx does not exist. #17161

GiteaMirror referenced this issue

2026-04-25 06:35:07 -05:00

[GH-ISSUE #14159] issue: Web search via searxng leads to chromadb.errors.InvalidCollectionException: Collection web-search-xxx does not exist. #32690

GiteaMirror referenced this issue

2026-05-05 18:07:56 -05:00

[GH-ISSUE #14159] issue: Web search via searxng leads to chromadb.errors.InvalidCollectionException: Collection web-search-xxx does not exist. #55827

GiteaMirror referenced this issue

2026-05-13 03:43:25 -05:00

[GH-ISSUE #14159] issue: Web search via searxng leads to chromadb.errors.InvalidCollectionException: Collection web-search-xxx does not exist. #71765