Accept upstream's architectural refactors:
- Settings UI sections moved from Python to frontend components
- User data consolidated under /usr directory
- Inline settings modal replaced by stacked modal system
- settings.js removed (moved to component stores)
Conflicts resolved by accepting upstream for all 5 files.
Our skills/backup features will be re-implemented using the new architecture.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit completes the replacement of Agent Zero's legacy "instruments"
system with the open SKILL.md standard (originally developed by Anthropic).
- Remove INSTRUMENTS from Memory.Area enum, keep only SKILLS
- Update memory.py to load skills instead of instruments
- Update memory_consolidation.py docstrings
- Delete agent.system.instruments.md (deprecated)
- Update solving.md: "prefer skills" instead of "prefer instruments"
- Update tips.md: Skills section with SKILL.md standard reference
- Update tool.skills.md: Cross-platform compatibility note
- architecture.md: Full rewrite of Skills section with SKILL.md format
- installation.md: Update directory structure references
- extensibility.md: Update component terminology
- README.md: Update navigation links
- Update memory dashboard filter options (instruments → skills)
- Update area color mappings
- .gitignore: Update skill patterns (builtin instead of default)
- .dockerignore: Same patterns
- backup.py: Update backup include patterns
- Cross-platform: Works with Claude Code, Cursor, Goose, Codex CLI
- YAML frontmatter for structured metadata
- Semantic recall from vector memory
- Token efficient (not in system prompt)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Updated the settings UI to work with the new backend format that separates settings values from additional metadata.
- Settings components now read from the new structure (settings + additional)
- Removed legacy field-based rendering in favor of direct value binding
- Root passwd masking
- Added knowledge subdirectory selector support
- Enhanced backend `convert_out()`: now ensures current values are always present in dropdown options, preventing UI glitches
- Cleaned up old conversion functions marked for removal
- Simplified task detail opening logic by integrating it into the `settingsModalStore`
- Updated the visibility condition for the task detail view in `scheduler-task-detail.html` to rely solely on the selected task state
rm attributes from components
simplify task display logic
settings components init
scheduler componentize
- Removed the inline scheduler settings script from `index.html` and replaced it with a new component structure in `scheduler-settings.html`, `scheduler-task-editor.html`, `scheduler-task-list.html`, and `scheduler-task-detail.html`.
- Introduced a dedicated `scheduler-store.js` to manage state and logic for the scheduler, enhancing maintainability and separation of concerns.
- Updated the `index.js` to remove the now obsolete `openTaskDetail` function, integrating task detail handling within the new store.
- Removed the deprecated `scheduler.js` file, consolidating functionality into the new component architecture.
settings modal store rename
- Replaced all instances of `$store.settingsModalStore` with `$store.settingsStore` across various settings components.
scheduler tab content x-if
Adressed:
1) When selecting memories using checkbox, it unchecks one second later automatically (Brave+Firefox)
2) Area filter does not work. When All is selecter, it shows me memories from fragments, solutions, etc., but when I select an area, no memories are shown.
3) Modal does not have a title, it shows a path
4) In light mode, buttons and some labels are almost invisible - we should not use custom colors anywhere, we should always use one of the color vars in the screenshot, those are automatically adjusted based on current theme. Also in light mode there's a lot of gray areas that blend, again, we should use our color vars.
5) The loading spinner is stretched into an oval
6) We should merge the first div (title and memory counts) with the third one (pagination) to save space. + we should also show the total number of memories in the DB (unfiltered, just the total count of docs)
7) Action buttons should stack vertically, we can remove the title to make it more narrow
8) We should not use emojis for icons, they break the design, it's used in the source badge (knowledge, conversation...)
fixed / adjusted:
1) After restart, it says that I need to use the agent first and also the memory subdirectory is selected based on current chat context. Instead there should be a selector of memory subdir before Area filter and the memory should be instantiated with first search. Meaning adding a Search button (just rename apply filters) and showing some loading indicator if memory is being instantiated.
2) Limit set to 500 cannot be changed in UI, it seems like there is exactly 500 memories in the DB. It should be a field in filter.
3) Pagination overflows when there's over 12 pages. The easiest way would be to replace enumerated buttons it with a html Select containing all the pages and leave Previous and Next on the sides for easy clicking. Also pagination should repeat below the table, that should be easy as alpine can bind multiple elements to the same model property.
4) The layout of memory rows is very inefficient, I would recommend merging Area, Timestamp, Source into one column called Metadata. Also the text is barely visible, it should be primary text color. Actions should be limited to minimum required as it is static.
5) There should be a selection column for mass delete, copy and export. You can add property "selected" to each memory item, then a checkbox on the left bound to that property. When at least one memory is selected, we would show a new toolbar at the top below pagination that would show the number of selected memories (this would automatically work across pages thanks to the binding to alpine data), copy contents button, delete button, export to file button. There should also be a check/uncheck all checkbox in the header row so users can quickly select and delete all.
6) The detail modal should be opened by clicking anywhere on the memory row.
7) We should use standard modal functionality, not this custom one, it creates problems, for example clicking outside the detail modal now closes even the dashboard. You can use the same data store, just fill a property like "detailMemory" there and open a modal that uses it. It will also be cleaner to have the modal HTML in another file.
8) The detail modal itself looks good. It should show all metadata in the memory (i don't know if currently there are only selected few or if it shows all, maybe it does).
9) Pressing enter in search field does not trigger the search.
10) Buttons on the right of filter are different height than inputs.
