@pi-claudian/auto-save-to-markdown 0.2.0 → 0.3.1

package/README.md

@@ -88,28 +88,30 @@ The login page redirects in a loop after the auth refactor...
 Assistant · 13:05:40 · claude-sonnet-4-5
 ===
 
-<details>
-<summary>Thinking</summary>
-
-Let me check the redirect chain...
-
-</details>
+> [!tldr]- Thinking
+>
+> Let me check the redirect chain...
 
 I'll trace the middleware order first.
 
-**Tool calls**
-
-- `read` — {"filePath":"/Users/me/project/src/auth/middleware.ts"}
-
-> **Tool · read** /Users/me/project/src/auth/middleware.ts — 120 lines …
+> [!quote]- Tool Calls · 1 (read)
+> **`read`** `{"filePath":"/Users/me/project/src/auth/middleware.ts"}`
+>
+> > `import { NextResponse } from "next/server"; export function middleware(…) …`
 
 ---
 ```
 
-The body renders user and assistant messages in full (assistant thinking is
-kept in a collapsible `<details>` block) and summarizes each tool call and
-result in one line, so the file stays readable while still showing what the
-agent did.
+The body renders user and assistant messages in full (assistant thinking and
+per-turn tool calls are each folded into a collapsed Obsidian callout —
+`> [!tldr]- Thinking` and `> [!quote]- Tool Calls · …`) and summarizes each
+tool call and result in one line, so the file stays readable while still
+showing what the agent did. Callouts are used instead of HTML `<details>`
+because Obsidian renders markdown inside HTML blocks unreliably; outside
+Obsidian the callouts degrade to plain blockquotes. Result and argument
+previews are wrapped in inline code spans (with a delimiter sized to survive
+backticks inside the content), so raw tool output renders literally instead of
+being parsed as markdown.
 
 Each message block opens with a setext level-1 info header (`User · …`,
 underlined with `===`) — one level above the `##` headings AI content

package/README.zh.md

@@ -78,27 +78,28 @@ auth 重构之后登录页一直重定向死循环……
 Assistant · 13:05:40 · claude-sonnet-4-5
 ===
 
-<details>
-<summary>Thinking</summary>
-
-先看中间件的执行顺序……
-
-</details>
+> [!tldr]- Thinking
+>
+> 先看中间件的执行顺序……
 
 我先追踪一下中间件链。
 
-**Tool calls**
-
-- `read` — {"filePath":"/Users/me/project/src/auth/middleware.ts"}
-
-> **Tool · read** /Users/me/project/src/auth/middleware.ts — 120 lines …
+> [!quote]- Tool Calls · 1 (read)
+> **`read`** `{"filePath":"/Users/me/project/src/auth/middleware.ts"}`
+>
+> > `import { NextResponse } from "next/server"; export function middleware(…) …`
 
 ---
 ```
 
-正文完整渲染 user / assistant 消息（assistant 的 thinking 放在可折叠的
-`<details>` 块中），每个工具调用和结果各压缩成一行摘要，既可读又能看出
-agent 做了什么。
+正文完整渲染 user / assistant 消息（assistant 的 thinking 与每轮工具调用
+分别折叠在可折叠的 Obsidian callout 中——`> [!tldr]- Thinking` 和
+`> [!quote]- Tool Calls · …`），每个工具调用和结果各压缩成一行摘要，既可读
+又能看出 agent 做了什么。之所以用 callout 而不是 HTML `<details>`，是因为
+Obsidian 对 HTML 块内嵌 Markdown 的渲染不可靠；在非 Obsidian 环境下 callout
+退化为普通引用块。结果与参数预览会包在 inline code 里（分隔符长度会自动
+压过内容中的反引号序列），工具的原始输出因此按字面渲染，不会被当作
+Markdown 解析。
 
 每个消息块以 setext 一级信息头（`User · …`，下一行以 `===` 下划）开头——
 高于 AI 内容常见的 `##` 二级标题，解析时也能与内容中的 `#` 一级标题区分

package/index.ts

@@ -27,11 +27,17 @@
  * - Tool call/result folding: calls live in the assistant entry while their
  *   results are separate toolResult entries; saves pair them by toolCall id
  *   and fold each assistant block's calls, with a short result preview each,
- *   into one `<details><summary>Tool Calls</summary>` section. Previews stay
- *   short (500 chars): full content is one Obsidian link away, and oversized
- *   details bodies render unfolded in Obsidian. A result whose call was
- *   saved in an earlier file (mid-turn manual save) falls back to a
- *   standalone one-line block.
+ *   into one collapsed Obsidian callout (`> [!quote]- Tool Calls · …`).
+ *   Thinking folds the same way into `> [!tldr]- Thinking`. Callouts are used
+ *   instead of HTML `<details>` because Obsidian's views render embedded
+ *   markdown inside HTML blocks unreliably, while callouts fold and render
+ *   markdown in both Live Preview and Reading view. Outside Obsidian the
+ *   callouts degrade to plain blockquotes. Argument previews and result
+ *   previews are wrapped in inline code spans (delimiter sized to survive
+ *   backticks inside the content), so raw output renders literally instead
+ *   of being parsed as markdown. A result whose call was saved in
+ *   an earlier file (mid-turn manual save) falls back to a standalone
+ *   one-line block.
  * - Branching: each file records exactly ONE branch (the root→leaf path
  *   returned by sessionManager.getBranch()). State is persisted via
  *   `pi.appendEntry()` custom entries, which are part of the session tree
@@ -290,6 +296,19 @@ export default function (pi: ExtensionAPI) {
 
   // ---------- markdown rendering ----------
 
+  /**
+   * Inline code span for arbitrary raw output (tool results, argument JSON):
+   * the delimiter is always one backtick longer than the longest backtick run
+   * inside the text, so content that itself contains backticks cannot break
+   * the span. Tool output renders literally instead of being parsed as
+   * markdown (headings, bold, wiki links …).
+   */
+  function inlineCode(text: string): string {
+    const longest = (text.match(/`+/g) ?? []).reduce((a, r) => Math.max(a, r.length), 0);
+    const fence = "`".repeat(longest + 1);
+    return `${fence}${text}${fence}`;
+  }
+
   /**
    * Strip leading blank lines and trailing whitespace from a rendered block,
    * so joins and separators always keep exactly one blank line around them
@@ -322,7 +341,7 @@ export default function (pi: ExtensionAPI) {
 
   /** Standalone one-line block for a result whose call is not in this file. */
   function renderToolResult(m: ToolResultMessage): string {
-    return `> **Tool · ${m.toolName}** ${resultPreview(m)}`.trim();
+    return `> **Tool · ${m.toolName}** ${inlineCode(resultPreview(m))}`.trim();
   }
 
   /** "read, web_search ×2" — tool names with repeat counts, first-seen order. */
@@ -333,21 +352,30 @@ export default function (pi: ExtensionAPI) {
   }
 
   /**
-   * Fold tool calls and their paired results into one collapsible section.
-   * Deliberately compact: Obsidian only collapses a details body it can
-   * render in view, so long previews make the section render unfolded.
+   * Collapsed Obsidian callout (`> [!type]- title`) wrapping a markdown body:
+   * every body line is prefixed with `>` (empty lines become bare `>`), so the
+   * body keeps rendering as markdown while folding works in both Obsidian
+   * views. Outside Obsidian the callout degrades to a plain blockquote.
+   */
+  function callout(type: string, title: string, body: string): string {
+    const lines = body.split("\n").map((line) => (line ? `> ${line}` : ">"));
+    return `> [!${type}]- ${title}\n${lines.join("\n")}`;
+  }
+
+  /**
+   * Fold tool calls and their paired results into one collapsed callout.
+   * Argument JSON and result previews are wrapped in inline code spans, so
+   * raw output renders literally instead of being parsed as markdown.
    */
-  function renderToolCallsDetails(calls: RenderedToolCall[]): string {
+  function renderToolCallsCallout(calls: RenderedToolCall[]): string {
     const summary = summarizeToolNames(calls.map((c) => c.name));
     const items = calls.map((c) => {
-      const head = c.args ? `**\`${c.name}\`** \`${c.args}\`` : `**\`${c.name}\`**`;
-      const result = c.result === null ? "_(no result)_" : c.result || "_(empty result)_";
+      const head = c.args ? `**\`${c.name}\`** ${inlineCode(c.args)}` : `**\`${c.name}\`**`;
+      const result =
+        c.result === null ? "_(no result)_" : inlineCode(c.result || "_(empty result)_");
       return `${head}\n\n> ${result}`;
     });
-    return (
-      `<details>\n<summary>Tool Calls · ${calls.length} (${summary})</summary>\n\n` +
-      `${items.join("\n\n")}\n\n</details>`
-    );
+    return callout("quote", `Tool Calls · ${calls.length} (${summary})`, items.join("\n\n"));
   }
 
   function renderAssistant(
@@ -364,9 +392,7 @@ export default function (pi: ExtensionAPI) {
     const thinkings: string[] = [];
     const flushThinking = () => {
       if (thinkings.length) {
-        parts.push(
-          `<details>\n<summary>Thinking</summary>\n\n${thinkings.join("\n\n")}\n\n</details>`,
-        );
+        parts.push(callout("tldr", "Thinking", thinkings.join("\n\n")));
         thinkings.length = 0;
       }
     };
@@ -389,7 +415,7 @@ export default function (pi: ExtensionAPI) {
       }
     }
     flushThinking();
-    if (calls.length) parts.push(renderToolCallsDetails(calls));
+    if (calls.length) parts.push(renderToolCallsCallout(calls));
     if (m.errorMessage) parts.push(`> Error: ${m.errorMessage.replace(/\s+/g, " ").trim()}`);
     if (parts.length === 0) parts.push("_(empty response)_");
     return `${header}\n\n${parts.join("\n\n")}`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-claudian/auto-save-to-markdown",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "description": "Pi extension that automatically saves each completed conversation turn as a markdown file with YAML frontmatter, one file per session-tree branch.",
   "type": "module",
   "license": "MIT",