Bug: Auto name lists for AI Mode

[amhsirak]

Currently, when performing a capture list action, the list and its fields are labeled generically (e.g., “List 1”, “Label 1”, “Label 2”), and users must rename them manually. We need to automatically generate meaningful list and field names based on context using an LLM. It should support multiple providers (Anthropic, OpenAI, OpenRouter, Ollama, etc.) and fall back to the default labeling if the LLM call fails.

[shivam-core]

Hi @amhsirak,

I would love to tackle this issue for FOSS Hack 2026.

My background is heavily rooted in ML and AI architectures, so I'm very interested in improving the AI Mode experience. Auto-naming these lists correctly will be a great quality-of-life upgrade for users relying on the AI extraction features.

I am setting up my local environment today and will be focusing on this project for the month. Could you please assign this to me? Also, if you could point me toward the specific file or module where the AI list generation currently happens, I would really appreciate the head start!

[RohitR311]

Hey, @shivam-core all the AI mode functionality currently lives in workflowEnricher.ts. The logic for auto-naming the list data generated during a capture list element action should ideally sit there as well. On the client side, you’ll want to check BrowserWindow.tsx and DOMBrowserRenderer.tsx for the auto generated fields when performing capture list. Also, this feature needs to work with the SDK. You can find the relevant routes in api/sdk.ts. Let me know if anything’s unclear.

[shivam-core]

Awesome, thank you for assigning this to me, @amhsirak!

And thank you for the exact file pointers, @RohitR311, that is incredibly helpful context. I will start by tracing the logic in workflowEnricher.ts and ensure the client-side components and SDK routes align with the new auto-naming logic.

I will keep posting my progress updates here and will reach out if I hit any roadblocks or if anything is unclear!