Skip to content

feat: dual-stream mindmap output with JSON mode and mindmap-as-context#6

Merged
web4zn merged 1 commit intomainfrom
opencode
May 7, 2026
Merged

feat: dual-stream mindmap output with JSON mode and mindmap-as-context#6
web4zn merged 1 commit intomainfrom
opencode

Conversation

@web4zn
Copy link
Copy Markdown
Owner

@web4zn web4zn commented May 7, 2026

  • Single API call produces both chat answer and full updated mindmap tree
  • JSON mode (response_format: json_object) for providers that support it
  • Fallback marker mode for other providers
  • Mindmap tree replaces raw conversation history as LLM context (60-80% token savings)
  • Removed corpus, batch generation, knowledge-applier, and all intermediate types
  • Simplified MindMap data model (monitoredConversationIds only)
  • Conversation-mindmap association via new dialog and panel
  • Edited node preservation via findEditedNodes/mergeEditedNodes
  • Increased dagre layout spacing for dense trees

Summary

Brief description of the change and why it's needed.

Related Issue

Fixes # (issue number)

Type of Change

  • Bug fix
  • New feature
  • Refactoring
  • Documentation
  • Other (please describe):

Checklist

  • I have tested my changes locally (npm test)
  • TypeScript compiles clean (npx tsc --noEmit)
  • I have updated documentation if needed
  • This PR follows existing code patterns in the project

- Single API call produces both chat answer and full updated mindmap tree
- JSON mode (response_format: json_object) for providers that support it
- Fallback <!--MINDMAP--> marker mode for other providers
- Mindmap tree replaces raw conversation history as LLM context (60-80% token savings)
- Removed corpus, batch generation, knowledge-applier, and all intermediate types
- Simplified MindMap data model (monitoredConversationIds only)
- Conversation-mindmap association via new dialog and panel
- Edited node preservation via findEditedNodes/mergeEditedNodes
- Increased dagre layout spacing for dense trees
@web4zn web4zn merged commit 4876c01 into main May 7, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant