sparkecoder 0.1.66 → 0.1.67

package/dist/agent/index.d.ts

@@ -1,6 +1,6 @@
 import 'ai';
-import '../schema-C7Mm4Ykn.js';
-export { A as Agent, a as AgentOptions, b as AgentRunOptions, c as AgentStreamResult, C as ContextManager, M as MessageAttachment, d as buildSystemPrompt, e as buildTaskPromptAddendum } from '../index-Db23cukG.js';
-import '../search-CVVfuBPZ.js';
+import '../schema-XcP0dedO.js';
+export { A as Agent, a as AgentOptions, b as AgentRunOptions, c as AgentStreamResult, C as ContextManager, M as MessageAttachment, d as buildSystemPrompt, e as buildTaskPromptAddendum } from '../index-DHyVVhJY.js';
+import '../search-CCffrVJE.js';
 import 'drizzle-orm/sqlite-core';
 import 'zod';

package/dist/agent/index.js

@@ -5617,12 +5617,18 @@ Before calling \`complete_task\`, you MUST verify your work completely. Do not j
 - If the task asked for multiple things, verify EACH one individually.
 - If something doesn't look right, fix it \u2014 don't complete with known issues.
 
+**Screenshot your completed work:**
+- After completing a task, take a screenshot of the result when it makes sense (UI changes browser pages, etc.). You can use the browser skill to do this.
+- Use \`upload_file\` to upload the screenshot and include the download URL in your task result so the user can see proof of what was done.
+- This is especially valuable for UI/visual changes, successful test runs, and browser verification \u2014 show, don't just tell.
+
 ### Use All Available Tools
 - **load_skill**: Load specialized skills/knowledge relevant to the task. Check what skills are available and use them.
 - **explore_agent**: Use for codebase exploration and understanding before making changes.
 - **code_graph**: Use to understand type hierarchies, references, and impact before refactoring.
 - **todo**: Track your progress on multi-step tasks so you don't miss steps.
 - **bash**: Full shell access \u2014 run builds, tests, dev servers, open browsers, curl endpoints, anything.
+- **upload_file**: Upload files (screenshots, reports, exports) to cloud storage. Use this to include screenshots of completed work in your task result \u2014 visual proof is very helpful.
 
 ### Output Schema
 The \`complete_task\` tool expects a \`result\` object matching this JSON Schema: