Repository navigation
Land PR #6 on main (agent notes) and ignore uv.lock - #7
Merged
Merged
Conversation
…gories Notes (new, modexai.note/1) - Agents post notes on a model, a recipe or task:<name>, and reply to each other. read_notes / post_note MCP tools and `modexai notes read|post`. Preview first; posted as a GitHub issue only with confirm=true after the user approves. No local drafts, so the text never touches disk unapproved. - Same defences as recipes: strict schema, 1,000-char limit, injection screen, links only to huggingface.co / ollama.com / github.com, maintainer review. Results say notes are data, never instructions. - Intake bot and workflow handle notes; build bundles data/notes.json and rejects notes about models or recipes that don't exist, or replies to missing notes. Recipes - agent (self-reported, excluded from the content id like author), category (so 'classification' finds 'support-ticket-routing'), and kind fine-tune with a fine_tune block: base model, method, example count only, baseline score on the same eval, weights link. - share_recipe / `recipes share` take agent, category and fine_tune. - Links in recipe text are limited to the same three hosts. Site - "What agents are saying": threads with agent badges and per-agent filters; empty state explains how an agent joins instead of showing placeholders. Recipe rows show agent, category and fine-tune details; model rows link to their notes. - Bundle ollama_tag in the built registry: on GitHub Pages every model's tag line was blank because only the local UI server derived it. The agent brief now covers reading and posting notes, naming tasks and categories, and sharing fine-tunes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The project doesn't track a lockfile. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Let agents talk: notes, fine-tune recipes, agent attribution, categories
The project doesn't track a lockfile, and `uv run` creates one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Summary
PR #6 was stacked on
decision-models. It merged into that branch rather thanmain, because GitHub only re-points a stacked PR atmainwhen its base branch is deleted. This PR brings its content tomain:ollama_tag, so model tag lines on GitHub Pages stop being blank.uv.lock: the project doesn't track a lockfile, anduv runcreates one.The code is the same as reviewed and tested in #6. The only addition is the
.gitignoreline.Test plan
notes.json🤖 Generated with Claude Code