Trends/Signals UX, investigation templates & docs#26
Merged
Conversation
Boolean trends, searchable field picker, agent-driven charts, and a record-and-replay "investigate pattern" system — plus documentation. - Trends: boolean fields (e.g. isTokenExpired=false) chart as a 0/1 step line (engine maps true/false→1/0; renderer draws a step line with false/true axis). - Trends: "Pick a field" is now a type-to-search combobox (input + datalist) instead of a plain select. - Agent charts: new logan_trend_show MCP tool renders a trend as a cell in the user's Trends notebook (series/transitions/correlate), so the agent can build a vertical sequence; pushed via a new agent-trend-cell IPC. - Investigation templates: the api-server journals the agent's investigative tool calls; they can be saved as a named, parameterised, re-runnable template (~/.logan/investigate-templates) and replayed on any log. New investigationStore.ts + endpoints + 4 MCP tools (get_investigation_log/save/list/run) + an Investigate-panel "Saved patterns" UI (Save current / ▶ run / delete) wired over new IPC channels. - Docs/help: CLAUDE.md tool table, docs/AGENT_CHAT_GUIDE.md, new docs/INVESTIGATION_TEMPLATES.md, in-app Help (F1) "Analysis, Trends & AI" section, and README features. Build green (tsc + renderer bundle); trendEngine tests 16/16. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Build-green batch from this session (tsc + renderer bundle; trendEngine tests 16/16).
Trends
isTokenExpired=false) chart as a 0/1 step line — the engine maps true/false→1/0 and aggregates them; the renderer draws a step line with a false/true axis. (Previously blank.)Agent-driven charts
logan_trend_showMCP tool renders a trend as a cell in the user's Trends notebook (series / value-flips / correlate), so the agent can build a vertical sequence of charts. Pushed via a newagent-trend-cellIPC; agent cells get a 🤖 badge.Investigation templates (record → save → replay)
~/.logan/investigate-templates/) and replayed on any log.src/main/investigationStore.ts(model + disk CRUD + param resolution), api-server endpoints + replay engine (internal HTTP, recursion-guarded), 4 MCP tools (logan_get_investigation_log/save/list/run), and an Investigate-panel "Saved patterns" UI (💾 Save current / ▶ run / × delete) over new IPC channels.Docs & in-app help
docs/AGENT_CHAT_GUIDE.md, newdocs/INVESTIGATION_TEMPLATES.md, in-app Help (F1) "Analysis, Trends & AI" section, README features.Also includes earlier session fixes already described to the user. The Signals stacked/synced-cursor view is not in this PR — it's the next piece.
🤖 Generated with Claude Code