Repository navigation
feat(entities): place names by description with the LLM, and manage entities from chat - #65
Merged
Merged
Conversation
…ntities from chat A setup can match names by name, then by description: names the rules can't place go to the LLM with the entities' descriptions, their other names and what the namespace is about. In the self-organizing mode a name it places on a described entity becomes one of that entity's other names, so the rules place it from then on; without an LLM the rules decide. The assistant gets an entity_setup tool (a namespace's mode, types, own types and defined entities), and propose_entity_change can now describe an entity and its other names, hide it, or add a new entity to a namespace's list, all through approval cards. find_entities includes descriptions, other names and whether an entity is defined. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VmPYPheY7aGQv9TiA563P5
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
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.
Requested by Adeel · project thread
Description
Before: in a self-organizing namespace a new way of saying a known thing ("the big client") became a new entity, and the assistant could only merge, rename or retype entities.
After:
entity_setuptool (mode, types kept, own types, defined entities),find_entitiesincludes descriptions, other names and whether an entity is defined, andpropose_entity_changecan now describe an entity (description and other names), hide it, or define a new entity on a namespace's list, each through an approval card. Settings → AI assistant lists the new tool.The matching code (
entity_map.judge) is shared so the next PR can use it for fixed lists and the hybrid mode.Motivation and Context
Fifth of the small PRs for entity modes ("self organizing entities yet user manage them via UI or assistant chat and descriptive fields are used to map these"). Next: hybrid mode, and the model for fixed lists.
Types of changes
!in the title)Checklist:
tests/api/test_entity_matching.py, the fake LLM answers matching requests).docs/accordingly (processing.md, assistant.md).## UnreleasedinCHANGELOG.md.Local checks: backend 348 passed (only
test_office_and_text_files_become_documentsfails, as on main: this machine's LibreOffice); frontend jest 546 passed, eslint and tsc clean.🤖 Generated with Claude Code
https://claude.ai/code/session_01VmPYPheY7aGQv9TiA563P5
Generated by Claude Code