Skip to content

Reject placeholder list names from list grammar matches - #2784

Open
datduyng wants to merge 1 commit into
mainfrom
domnguyen/list-placeholder-reject
Open

Reject placeholder list names from list grammar matches#2784
datduyng wants to merge 1 commit into
mainfrom
domnguyen/list-placeholder-reject

Conversation

@datduyng

@datduyng datduyng commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Reject determiner/placeholder listName captures (the/my/list) via checked_wildcard + execute guards so bare list phrases fall through to the LLM while named lists still match.

- Treat determiner-only listName captures (the/my/list) as invalid via
  checked_wildcard validation so bare list phrases fall through to the LLM
- Normalize list names; execute-time guards; unit coverage for edge names
- Authored TODO in listSchema.agr + schema-tuning guide note #5
@robgruen

robgruen commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

Looking at this I think a better approach is to just remove the grammar rule that's causing the problem.

If I say: "create a ingedients list and a shopping list" and then "add cheese to both" that should work. The agent shouldn't know or care about any grammar or caching. In fact, it should work regardless of language. A user should be able to create a list called "my"... or, my could refer to a list of the useres name but that should get resolved in translation and not in the agent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants