@protolabsai/proto 0.18.0 → 0.18.1

package/bundled/qc-helper/docs/features/_meta.ts

@@ -1,5 +1,6 @@
 export default {
   commands: 'Commands',
+  export: 'Session Export',
   'followup-suggestions': 'Followup Suggestions',
   'sub-agents': 'SubAgents',
   arena: 'Agent Arena',

package/bundled/qc-helper/docs/features/commands.md

@@ -25,6 +25,7 @@ These commands help you save, restore, and summarize work progress.
 | `/compress` | Replace chat history with summary to save Tokens          | `/compress`                          |
 | `/resume`   | Resume a previous conversation session                    | `/resume`                            |
 | `/restore`  | Restore files to state before tool execution              | `/restore` (list) or `/restore <ID>` |
+| `/export`   | Export current session to a file (html, md, json, jsonl)  | `/export html`, `/export md`         |
 
 ### 1.2 Interface and Workspace Control
 

package/bundled/qc-helper/docs/features/export.md

@@ -0,0 +1,51 @@
+# Session Export
+
+The `/export` command saves your current session to a file in your working directory. Four formats are supported.
+
+## Usage
+
+```
+/export <format>
+```
+
+| Command         | Output                                             |
+| --------------- | -------------------------------------------------- |
+| `/export html`  | Self-contained HTML file with a rendered viewer    |
+| `/export md`    | Markdown — plain text, readable anywhere           |
+| `/export json`  | Structured JSON — one object per message           |
+| `/export jsonl` | JSONL — one JSON object per line (stream-friendly) |
+
+Files are written to the current working directory with a timestamped name, e.g. `export-2025-04-05T16-30-00-000Z.html`.
+
+## HTML Format
+
+The HTML export produces a **self-contained file** — no server, no internet connection required to view it. Open it directly in any browser.
+
+It includes:
+
+- Full conversation history with role labels (user / assistant / tool)
+- Rendered markdown (code blocks, lists, headings)
+- Tool call inputs and outputs collapsed by default
+- A minimal, readable stylesheet baked in
+
+This is useful for sharing a session with teammates, archiving a debugging session, or reviewing a long conversation outside the terminal.
+
+## JSON / JSONL Formats
+
+These formats expose the raw message structure, useful for:
+
+- Piping into other tools (`jq`, scripts, LLM pipelines)
+- Programmatic analysis of session content
+- Building integrations on top of proto session data
+
+`json` outputs a single array. `jsonl` outputs one JSON object per line, which is better for streaming and large files.
+
+## Markdown Format
+
+Exports the conversation as a readable `.md` file. Good for pasting into notes, wikis, or GitHub issues.
+
+## Notes
+
+- Export captures the session state at the moment the command runs — messages added after export are not included.
+- The file is written to `config.workingDir` (the directory proto was started in).
+- No session data is sent anywhere — the file is written locally only.

package/cli.js

@@ -170762,7 +170762,7 @@ __export(geminiContentGenerator_exports, {
   createGeminiContentGenerator: () => createGeminiContentGenerator
 });
 function createGeminiContentGenerator(config2, gcConfig) {
-  const version2 = "0.18.0";
+  const version2 = "0.18.1";
   const userAgent2 = config2.userAgent || `QwenCode/${version2} (${process.platform}; ${process.arch})`;
   const baseHeaders = {
     "User-Agent": userAgent2
@@ -172612,19 +172612,7 @@ Produce a condensed summary of the entire conversation for seamless continuation
 
 ESSENTIAL: Reply with PLAIN TEXT ONLY. Do NOT invoke any tools. Tool invocations will be BLOCKED.
 Everything you need is already present in the conversation above.
-Output must be: one <analysis> block followed by one <summary> block.
-
-## Analysis Phase
-
-Before writing the summary, wrap your reasoning inside <analysis> tags:
-- Walk through each message chronologically
-- Identify what the user asked for and their underlying intent
-- Note the strategy or approach adopted
-- Record pivotal decisions and trade-offs
-- Capture technical concepts and patterns discussed
-- Extract concrete details: file paths, complete code fragments, function signatures, file modifications
-- Document errors encountered and how they were resolved
-- Note any user feedback or corrections
+Output must be a single <summary> block. Be maximally concise \u2014 every token counts.
 
 ## Summary Sections
 
@@ -172634,21 +172622,21 @@ The <summary> block must contain exactly these ten sections:
 
 2. **Key Technical Concepts** \u2014 Frameworks, patterns, algorithms, architectures, or domain knowledge involved. Include build commands, test commands, and environment details.
 
-3. **Files and Code Sections** \u2014 Enumerate every relevant file by absolute path. Include complete code snippets for anything non-trivial. Note status: CREATED, MODIFIED, READ, DELETED. Explain why each matters. For files that were read multiple times, keep only the most recent read \u2014 deduplicate by path.
+3. **Files and Code Sections** \u2014 Enumerate every relevant file by absolute path. Note status: CREATED, MODIFIED, READ, DELETED. For non-trivial changes, describe what changed and why \u2014 do NOT reproduce full file contents or long code listings. Only include short, critical snippets (< 20 lines) where the exact code is essential for resumption.
 
 4. **Errors and Fixes** \u2014 Every error that surfaced, the exact error message, how it was resolved, and any user reactions or corrections. This section prevents the agent from retrying failed approaches.
 
 5. **Problem Solving** \u2014 Reasoning chains, alternative approaches considered and why they were rejected, debugging strategies applied. This section preserves eliminated dead ends.
 
-6. **All User Messages** \u2014 List ALL non-tool-result messages from the user, preserving their substance verbatim. Do not paraphrase \u2014 the user's exact words carry intent that summaries lose.
+6. **All User Messages** \u2014 Summarize the intent and substance of each user message concisely. Preserve exact wording only for short, critical instructions \u2014 do not reproduce long messages verbatim.
 
 7. **Current Todo List** \u2014 List EVERY todo item with its exact current status: added | in_progress | completed | cancelled. Do not omit any item. This is critical for resuming work without re-planning completed tasks.
 
 8. **Pending Tasks** \u2014 Work that remains unfinished or was explicitly deferred. Include any promises made to the user.
 
-9. **Current Work** \u2014 Precise description of what was actively being worked on at conversation end, with file names, line numbers, and code fragments. This is the most critical section for seamless resumption.
+9. **Current Work** \u2014 Precise description of what was actively being worked on at conversation end, with file names and line numbers. This is the most critical section for seamless resumption.
 
-10. **Optional Next Step** \u2014 MUST align directly with the user's most recent explicit requests. Include direct quotes showing which task was underway. Do not invent next steps the user did not ask for.
+10. **Optional Next Step** \u2014 MUST align directly with the user's most recent explicit requests. Do not invent next steps the user did not ask for.
 
 ## Continuation Behavior
 
@@ -174031,7 +174019,7 @@ ${summary}`;
               role: "user",
               parts: [
                 {
-                  text: "First, reason in your scratchpad. Then, generate the <state_snapshot>."
+                  text: "Generate the <summary> now. Be maximally concise \u2014 every token counts."
                 }
               ]
             }
@@ -411779,7 +411767,7 @@ __name(getPackageJson, "getPackageJson");
 // packages/cli/src/utils/version.ts
 async function getCliVersion() {
   const pkgJson = await getPackageJson();
-  return "0.18.0";
+  return "0.18.1";
 }
 __name(getCliVersion, "getCliVersion");
 
@@ -419551,7 +419539,7 @@ var formatDuration = /* @__PURE__ */ __name((milliseconds) => {
 
 // packages/cli/src/generated/git-commit.ts
 init_esbuild_shims();
-var GIT_COMMIT_INFO = "9828e8f69";
+var GIT_COMMIT_INFO = "ea801e2ee";
 
 // packages/cli/src/utils/systemInfo.ts
 async function getNpmVersion() {
@@ -486320,7 +486308,7 @@ var QwenAgent = class {
   async initialize(args2) {
     this.clientCapabilities = args2.clientCapabilities;
     const authMethods = buildAuthMethods();
-    const version2 = "0.18.0";
+    const version2 = "0.18.1";
     return {
       protocolVersion: PROTOCOL_VERSION,
       agentInfo: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@protolabsai/proto",
-  "version": "0.18.0",
+  "version": "0.18.1",
   "description": "proto - AI-powered coding agent",
   "repository": {
     "type": "git",
@@ -21,7 +21,7 @@
     "bundled"
   ],
   "config": {
-    "sandboxImageUri": "ghcr.io/qwenlm/qwen-code:0.18.0"
+    "sandboxImageUri": "ghcr.io/qwenlm/qwen-code:0.18.1"
   },
   "dependencies": {},
   "optionalDependencies": {