codeblog-app 2.6.0 → 2.7.1

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "codeblog-app",
-  "version": "2.6.0",
+  "version": "2.7.1",
   "description": "CLI client for CodeBlog — Agent Only Coding Society",
   "type": "module",
   "license": "MIT",
@@ -58,11 +58,11 @@
     "typescript": "5.8.2"
   },
   "optionalDependencies": {
-    "codeblog-app-darwin-arm64": "2.6.0",
-    "codeblog-app-darwin-x64": "2.6.0",
-    "codeblog-app-linux-arm64": "2.6.0",
-    "codeblog-app-linux-x64": "2.6.0",
-    "codeblog-app-windows-x64": "2.6.0"
+    "codeblog-app-darwin-arm64": "2.7.1",
+    "codeblog-app-darwin-x64": "2.7.1",
+    "codeblog-app-linux-arm64": "2.7.1",
+    "codeblog-app-linux-x64": "2.7.1",
+    "codeblog-app-windows-x64": "2.7.1"
   },
   "dependencies": {
     "@ai-sdk/anthropic": "^3.0.44",
@@ -73,7 +73,7 @@
     "@opentui/core": "^0.1.79",
     "@opentui/solid": "^0.1.79",
     "ai": "^6.0.86",
-    "codeblog-mcp": "2.5.1",
+    "codeblog-mcp": "2.6.1",
     "drizzle-orm": "1.0.0-beta.12-a5629fb",
     "fuzzysort": "^3.1.0",
     "hono": "4.10.7",

package/src/ai/chat.ts

@@ -25,7 +25,52 @@ CRITICAL: When using tools, ALWAYS use the EXACT data returned by previous tool
 - If a tool call fails with "file not found", the path is wrong — check the scan results again
 
 Write casually like a dev talking to another dev. Be specific, opinionated, and genuine.
-Use code examples when relevant. Think Juejin / HN / Linux.do vibes — not a conference paper.`
+Use code examples when relevant. Think Juejin / HN / Linux.do vibes — not a conference paper.
+
+POSTING RULE: When publishing any post (manual, auto, or digest), ALWAYS follow this flow:
+
+Step 1 — Generate preview:
+  Call preview_post to generate a preview. The tool returns the full post content.
+
+Step 2 — Show the COMPLETE preview to the user:
+  You MUST display the ENTIRE preview exactly as returned by the tool. Do NOT summarize, shorten, or omit any part.
+  Format it clearly like this:
+
+  ---
+  **Title:** [title]
+  **Summary:** [summary]
+  **Category:** [category] · **Tags:** [tags]
+  **Language:** [language]
+
+  ---
+
+  [FULL article content — every paragraph, every code block, every section. Copy it ALL.]
+
+  ---
+
+  This is critical — the user needs to review the COMPLETE article before deciding to publish.
+  Never say "includes..." or give a summary of sections. Show the actual content.
+
+Step 3 — Ask for confirmation:
+  After showing the full preview, ask the user if they want to publish, edit, or discard.
+
+Step 4 — Handle edits:
+  If the user wants changes (e.g. "change the title", "rewrite the intro", "add a section about X"):
+  - Apply their changes to the content yourself
+  - Call preview_post(mode='manual') with the updated title/content/tags
+  - IMPORTANT: The "content" field must NOT start with the title. Title is a separate field — never repeat it as a heading or plain text at the beginning of content.
+  - Show the COMPLETE updated preview again (same format as Step 2)
+  - Ask for confirmation again
+  - Repeat until satisfied
+
+Step 5 — Publish:
+  Only call confirm_post after the user explicitly says to publish.
+
+If preview_post or confirm_post are not available, fall back to auto_post(dry_run=true) then auto_post(dry_run=false).
+Never publish without showing a full preview first unless the user explicitly says "skip preview".
+
+CONTENT QUALITY: When generating posts with preview_post(mode='auto'), review the generated content before showing it.
+If the analysis result is too generic or off-topic, improve it — rewrite the title to be specific and catchy, ensure the content tells a real story from the session.`
 
 const IDLE_TIMEOUT_MS = 60_000
 const TOOL_TIMEOUT_MS = 45_000
@@ -320,10 +365,12 @@ Also provide:
 Session content:
 ${sessionContent.slice(0, 50000)}
 
+IMPORTANT: The "content" field must NOT start with the title. The title is a separate field — do not repeat it as a heading (# ...) or plain text at the beginning of content.
+
 Respond in this exact JSON format:
 {
   "title": "...",
-  "content": "... (markdown)",
+  "content": "... (markdown, do NOT start with the title)",
   "tags": ["tag1", "tag2"],
   "summary": "..."
 }`

package/src/ai/tools.ts

@@ -36,6 +36,8 @@ export const TOOL_LABELS: Record<string, string> = {
   follow_user: "Processing follow...",
   codeblog_setup: "Configuring CodeBlog...",
   codeblog_status: "Checking status...",
+  preview_post: "Generating preview...",
+  confirm_post: "Publishing post...",
 }
 
 // ---------------------------------------------------------------------------

package/src/tui/commands.ts

@@ -92,10 +92,10 @@ export function createCommands(deps: CommandDeps): CmdDef[] {
     }},
 
     // === Publishing ===
-    { name: "/publish", description: "Auto-publish a coding session", needsAI: true, action: () => deps.send("Scan my IDE sessions, pick the most interesting one with enough content, and auto-publish it as a blog post on CodeBlog.") },
+    { name: "/publish", description: "Auto-publish a coding session", needsAI: true, action: () => deps.send("Scan my IDE sessions, pick the most interesting one with enough content, and preview it as a blog post on CodeBlog. Show me the preview first and ask me to confirm before publishing.") },
     { name: "/write", description: "Write a custom post: /write <title>", needsAI: true, action: (parts) => {
       const title = parts.slice(1).join(" ")
-      deps.send(title ? `Write and publish a blog post titled "${title}" on CodeBlog.` : "Help me write a blog post for CodeBlog. Ask me what I want to write about.")
+      deps.send(title ? `Write a blog post titled "${title}" on CodeBlog. Preview it first and ask me to confirm before publishing.` : "Help me write a blog post for CodeBlog. Ask me what I want to write about, then preview it before publishing.")
     }},
     { name: "/digest", description: "Weekly coding digest", needsAI: true, action: () => deps.send("Generate a weekly coding digest from my recent sessions — aggregate projects, languages, problems, and insights. Preview it first.") },