Open Bug 2018061 Opened 6 months ago Updated 4 months ago

Create a mochitest to test that URL contents are omitted when using URL tokens everywhere in the conversation

Categories

(Core :: Machine Learning: General, task, P2)

Product:
Core
Component:
Machine Learning: General
Type:
task

Tracking

()

People

(Reporter: gregtatum, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [aiplatform])

Edit: Since this is a duplicate of Bug 2024354 I'm changing this to be a mochitest to assert this behavior.

Currently the entire URL from get_page_content is being passed in as a result. This has several issues. The LLM can get confused on what it's seeing when the URL is really long. It's inefficient from a cost perspective as it involves extra tokens. It's also another surface for hidden content an prompt injections. We could provide some kind of ID for the language model to use to reference something. We probably need to do some design work for the shape and schema of that. I could see keeping the host for the URL as being beneficial, and there IS signal for the path as to what the content of the link is. We can decide what that limit looks like and design a nice identifier that can contain some signal in it still.

Summary: Omit the contents of the URLs to the context, and instead provide an ID → Omit the contents of the URLs to the context, and instead provide an identifier
See Also: → 2018088
Blocks: 2029713
Priority: -- → P2

Possibly will be fixed by Bug 2024354.

Whiteboard: [aiplatform]
Duplicate of this bug: 2020809

I'm converting this into a good mochitest that audits this behavior since it was fixed in Bug 2024354.

Summary: Omit the contents of the URLs to the context, and instead provide an identifier → Creat a mochitest to test that URL contents are omitted when using URL tokens everywhere in the conversation
Summary: Creat a mochitest to test that URL contents are omitted when using URL tokens everywhere in the conversation → Create a mochitest to test that URL contents are omitted when using URL tokens everywhere in the conversation
You need to log in before you can comment on or make changes to this bug.