Explain Agenttrail observability and compare Map with Kitchen - #12
Merged
Conversation
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.
The README introduced the kitchen before clearly explaining Agenttrail's purpose and the relationship between its two views. It also blurred their provider coverage and privacy behavior.
Lead with local observability: Agenttrail observes coding agents working in their existing tools and visualizes available evidence. Add a Map/Kitchen comparison with the two commands, plus a data-source diagram and guide covering native todos, durable plans, inferred roles, actual sessions, local storage and current integration limits. Correct Map's source package description, modern Claude task coverage and setup side effects. Preserve the screenshots, cooking clip and existing preview instructions.
A focused repository review reproduced four open runtime issues and recorded follow-up tasks in PLAN.md. The detailed reproduction report is local; this change updates documentation and metadata only. It does not claim those runtime issues are fixed.
Validation: 38 local documentation links checked; Map syntax and package metadata checked; all 71 existing Kitchen tests pass. Separate isolated reproductions confirmed request validation, Map/Kitchen task precedence, hook detection and plan acknowledgement gaps. CI additionally exercises the packaged Kitchen on Linux and macOS.