Concept Roamer

Concept Roamer / 概念漫游

Discuss concepts with DeepSeek in Obsidian and turn a conversation into an editable Markdown concept note. Connect the note to existing notes and keep a linked conversation summary.

中文说明

Features

• Streaming chat with cancellation and recovery of interrupted replies.
• Editable personality and a shared, manually maintained memory note.
• Concept notes covering definitions, mechanisms, examples, boundaries, applications, and open questions.
• Preview and edit generated Markdown before saving.
• Suggestions for links to existing notes, plus a conversation summary.
• Separate export of the original conversation.
• Automatic conversation titles that evolve with the discussion, plus manual naming.
• Manual and automatic context compression, with inspectable summaries and retained original messages.
• Discuss selected note excerpts from the context menu, with a source card and retained context for follow-up questions.
• Desktop pop-out chat using Obsidian's window support.
• Pale pink user bubbles, spacious AI reading cards, and collapsible note excerpts, with light and dark theme support and layouts for narrow panes.
• Update a previously saved concept note from new discussion, with paragraph changes, an editable full preview, original-version backups, and conflict checks.

Requirements and external service

Requires Obsidian 1.11.4 or later and your own DeepSeek API key. DeepSeek account access and API usage may require payment. The plugin itself does not include API credits.

Requests go directly to https://api.deepseek.com/chat/completions. Chat requests send your messages, personality note, manual memory note, and the selected conversation branch. Messages with note excerpts also send the selected text, note title, and relative vault path. Choosing 在漫游中讨论 stages the excerpt locally; pressing 发送 submits it with your question. Concept organization also sends snippets of up to eight relevant Markdown notes, selected by titles, aliases, and quoted sources. Quoted source candidates use the selected excerpt; other candidates use opening snippets. A separate model request is made when you click 开始整理.

Automatic titles are enabled by default. Naming runs in the background after the first complete reply, then after every three additional complete replies. Opening an older conversation can also name it if it has no generated title. Each naming operation makes an additional DeepSeek request with bounded opening and recent conversation excerpts, without the personality or memory notes; normal API charges apply. Disable it in settings or use 标题 to save a fixed manual title. Naming failures preserve the current title and do not block chat.

The plugin does not include analytics, a developer-operated proxy, or an updater. DeepSeek handles submitted content according to its own service terms and privacy policy.

The API key is managed through Obsidian SecretStorage. Plugin settings store the secret's name. Conversation JSON, generated notes, personality, and memory live inside your vault under 概念漫游/. Recovery drafts are stored locally through Obsidian's local storage API.

Context compression

Select 上下文 in the chat toolbar to compress earlier discussion, inspect the summary, view covered original messages, or rebuild from originals. Chat displays, transcript export, and concept organization continue to use the complete original records. Summaries are lossy AI material; check the original messages when details matter.

使用压缩上下文 and 自动压缩长对话 are enabled by default. When effective history plus the current question exceeds approximately 32,000 characters, the plugin attempts compression before saving or sending that question. This is a character budget, not a token estimate; personality and manual memory are separate. It normally keeps the latest four complete turns verbatim, reducing that number for large recent turns while retaining the latest complete turn and unanswered questions. A first summary needs at least two older completed turns.

Compression makes additional DeepSeek requests containing earlier discussion from the selected branch and any existing summary, without personality, manual memory, or the unsent question. A batch contains at most 40,000 JSON characters of new material, with at most four batches per operation and a two-minute timeout per batch. There is no automatic paid retry. Interrupted, invalid, or non-reducing results are not adopted. 停止压缩 cancels from the modal; 停止 also works in chat. Completed batch checkpoints may be retained for the next attempt.

Summaries separate AI explanations, exact user quotations, unresolved questions, and disagreements. Exact user quotations are checked against typed user messages; note excerpts and assistant replies cannot be attributed as user quotations. Incremental compression retains previously extracted user quotations. This validation cannot guarantee the accuracy or completeness of the AI's narrative summary.

Summary JSON is saved under 概念漫游/会话/<session ID>/上下文/, with source message IDs and a SHA-256 content fingerprint. Only an unchanged, fully available prefix of the selected conversation branch can use a summary. Switching branches, incomplete synchronization, or changed source content prevents an unrelated summary from being applied.

Rebuilding from originals starts a new summary lineage. Later sends, reloads, and incremental compression continue that lineage, even when an older summary covered more messages. Very large old conversations may need multiple operations; after four completed batches, select 压缩上下文 to continue from the new checkpoint. Previous summary files are retained.

On automatic compression failure, the plugin explicitly falls back to complete original history only if it fits the 80,000-character history-plus-question budget. Otherwise the unsent question remains unaccepted and the plugin requests manual compression or a new conversation. It does not silently truncate history. Disabling automatic compression still permits manual compression and existing summaries; disabling compressed context restores complete history without deleting summaries. Both settings affect all conversations, starting with the next send. Archive files themselves are not compressed.

Installation and use

For manual installation, copy main.js, manifest.json, and styles.css from a GitHub release into .obsidian/plugins/concept-roamer/ inside your vault, then enable Concept Roamer in Community plugins. The chat interface and commands use Chinese labels.

1. Set your DeepSeek key and a model available to your account in plugin settings.
2. Open the chat with the ribbon icon or the 打开聊天 command.
3. Enter sends a message; Shift+Enter inserts a newline.
4. After a discussion, select 整理并保存, optionally specify a concept, and click 开始整理.
5. Review or edit the result, then select 保存到知识库.

Concept notes are saved in 概念漫游/概念/; conversation summaries are stored alongside the corresponding session. Existing files are preserved when names conflict.

Continue updating a concept note

After further discussion in the same conversation, select 整理并保存 → 更新已有笔记, choose an associated concept note, and select 整理修订. Review each proposed paragraph change and the complete preview, optionally edit the final body, then select 确认更新原笔记. 保存为新笔记 remains available for a separate concept. Only previously associated notes are update targets; unrelated vault files cannot be selected. Legacy concept notes are recognized through their existing metadata, including after a rename or move.

Updating makes an additional DeepSeek request with the note's current body, new messages after its last covered discussion, and up to eight related-note snippets. It does not send frontmatter or previously covered chat. Normal API charges apply, with no automatic paid retry. Requests are limited to 140,000 serialized prompt characters. The model proposes exact paragraph replacements rather than rewriting the whole note; unchanged text and frontmatter are retained. Source links and extracted user quotations are validated, but this cannot guarantee semantic accuracy or completeness. Check personal statements before saving.

Save compares the original snapshot inside Obsidian's vault.process, following the official file modification guidance; an intervening manual or synchronized change blocks replacement. The exact previous note is saved under the session's 笔记版本/, with immutable coverage records in 笔记修订/ and a discussion summary in 整理摘要/. A failed record or summary save can be retried after reopening without repeating the body update. 丢弃修订草稿 clears only the local draft, leaving saved notes and backups intact.

Keep concept_id and session_id in the note's frontmatter. Multiple files with the same concept ID, another conversation branch, modified source messages, missing revision parents, or concurrent revision tips prevent an automatic update. Complete synchronization and reopen the organizer, or save a new note with a new ID. Revision ancestry determines coverage, independently of device clock order. Archive files are retained.

To discuss a note, select text in editing, live preview, or reading mode and choose 在漫游中讨论 from the context menu. This starts a new conversation for the excerpt. The plugin reuses an open chat window; desktop creates a pop-out if no chat is open, and mobile opens a chat tab. Review the source card, enter a question, and press 发送. Sending just the excerpt requests an explanation. The source card links back to the note; 移除 detaches it. Use 在当前漫游中继续 to add the selection to the current conversation instead. The previous conversation stays in history, and returning to it in the same view restores its unsent question and selection. Start a new discussion after the current reply is saved; the continuation option can stage an excerpt while a reply is running. Excerpts are limited to 8,000 characters and count toward the message and conversation budgets. For Android, the commands 在漫游中讨论选中文字 and 在当前漫游中继续讨论选中文字 provide additional entry points.

Saved messages retain the excerpt separately from the typed question, including its source. Follow-up questions, conversation export, automatic naming, and concept organization can use it. Selecting an excerpt alone does not establish the user's authorship or agreement with it.

Quoted excerpts appear before the question in sent messages. Excerpts longer than 240 characters start collapsed; select the card header to expand or collapse them. The source and remove buttons operate independently of folding. Code blocks and wide tables scroll within the reply card.

Sources mentioned in the conversation are marked as unverified. Review model output before relying on it. Automated memory extraction and lossless archive compression are not included in this release.

Compatibility and validation

Windows uses a desktop-only HTTPS transport; Android uses browser fetch and ReadableStream. Desktop Node APIs are guarded by Platform.isDesktopApp.

Version 0.2.4 fixes the desktop module-loading failure exposed by upgrading from 0.2.0. The build lowers guarded imports to CommonJS loading, so the renderer does not resolve Node modules as browser URLs. Runtime errors retain their details; browser connection failures are handled at the request boundary.

The current build passes 181 local tests, including paragraph updates, coverage ancestry, conflict checks and retry protection, context compression, branch fingerprints, rebuild continuation, cancellation, original-history fallback, compiled desktop requests, note selection, fresh discussion isolation, excerpt persistence, input limits, and concurrent selection handling. Chrome checks using a simulated Obsidian host and model covered manual and automatic compression, original-message viewing, safe plain-text summary display, modal cancellation, reload, branch isolation, and disabled compression at desktop and narrow widths. Existing selection menus, source cards, automatic titles, concept editing and saving, reading behavior, and module routing also have simulated-host coverage. Real DeepSeek summary quality, Android WebView streaming, selection menus, and device synchronization still require actual-use validation. Desktop behavior has been tried by the project owner; this does not establish compatibility across other installations.

Version 0.2.8 also has simulated-host UI checks in both light and dark themes at widths of 320, 390, 620, and 820 pixels. These covered user text contrast, rich Markdown overflow, excerpt folding and keyboard operation, composer layout, and preservation of reading position during streaming. Actual Obsidian themes and Android devices still need use on the target installation.

Development

npm ci
npm run build
npm test

Output: dist/concept-roamer/.

License

MIT. See LICENSE. Copyright 2026 F1ameyqq.