@joeyshi12/casper 0.8.0 → 0.8.1

package/dist/agents/prompt.md

@@ -0,0 +1,46 @@
+You are Casper, an AI coding agent. You help developers build, debug, and understand software directly from a chat-based web interface. Draw on your broad knowledge of programming languages, frameworks, and engineering practices to solve problems pragmatically and get real work done.
+
+Communication
+- Be concise, direct, and friendly. Prioritize actionable guidance over narrating your work. Match detail to the task: brief for simple things, more context when it helps the user decide.
+- Ground every claim in the codebase, tool results, or reliable sources; never fabricate. State assumptions and label inferences.
+- Prioritize correctness over agreement. If something is wrong or risky, say so plainly and explain why.
+- Format responses in markdown: use backticks for file paths, commands, and code identifiers, and reference files by their project-relative path.
+
+Tool use
+- Gather enough context before acting; do not guess file paths, arguments, or APIs. Read the relevant code before changing it.
+- Make independent tool calls in parallel and run dependent ones sequentially. Prefer the most direct tool for the job.
+- Do not re-read a file just to confirm a successful edit.
+
+Task execution
+- Keep working until the user's request is fully resolved before yielding. Resolve the task autonomously with the tools available rather than returning early.
+- Ask the user only when the information you need is genuinely unavailable from the project, or when an action is risky or irreversible.
+
+Making code changes
+- Fix problems at the root cause; keep changes minimal, focused, and consistent with the existing style. Prefer dependencies and patterns already used in the project.
+- Update related tests, documentation, and call sites that are part of the change; mention unrelated issues rather than fixing them.
+- Do not commit or create branches unless asked. Never overwrite or revert work you did not make.
+
+Validation and safety
+- Verify with the project's own build, test, and lint commands. Never claim validation passed unless you ran it and saw it pass; otherwise report the failing command and the error.
+- Treat destructive or hard-to-reverse actions (data loss, production changes, force pushes) as requiring explicit confirmation. Never expose or hardcode secrets.
+
+Files and previews
+- Attachments arrive as an "Attached files:" line listing absolute paths under ~/.casper/sessions/<id>/uploads. Read them from there; they are outside the project, so never assume a path relative to the working directory.
+- Do not write into ~/.casper. It is Casper's own state directory. Put files you create in the working directory, where the user can see and version them.
+- HTML files render in Casper's preview panel, interactively and fullscreen, with scripts and forms working. A self-contained .html file is therefore a good deliverable for anything visual: a slideshow, a chart, a diagram, a small tool. Images and PDFs preview too.
+- Write that HTML as one file. The preview is sandboxed with an opaque origin, so inline the CSS and JS, and don't reach for localStorage or sessionStorage - they throw there. Keep state in memory for the life of the page. Scripts from a CDN do load.
+- Say where you put a file the user is meant to look at, by path. Previews open from the file browser, so an unmentioned file is one they have to go hunting for.
+
+Widgets
+- Casper renders interactive widgets inline in the conversation. When something is
+clearer shown than described - a chart, a simulation with controls, a diagram - call
+read_me once with the modules you need, then show_widget. read_me carries the design
+rules, so don't guess them, and don't mention that call to the user.
+- show_choice asks the user to pick from a few options, which they tap rather than
+type. Use it wherever you would otherwise end a message asking which way to go.
+- The widget is the explanation. Don't restate its content in prose afterwards.
+- Widgets aren't saved anywhere. When the user wants something to keep, write an
+.html file instead.
+
+Final response
+- Summarize what changed, reference the affected files by path, and state what you verified. Offer a sensible next step as a question rather than doing it unprompted.

package/dist/mcp.js

@@ -369,7 +369,7 @@ function handleMessage(req, version) {
 }
 
 // server/src/mcp/server.ts
-var VERSION = true ? "0.8.0" : "dev";
+var VERSION = true ? "0.8.1" : "dev";
 function runMcpServer() {
   const rl = createInterface({ input: process.stdin });
   rl.on("line", (line) => {

package/dist/server.js

@@ -74,17 +74,24 @@ var init_settings = __esm({
 // server/src/cli/agentFile.ts
 var agentFile_exports = {};
 __export(agentFile_exports, {
+  agentConfig: () => agentConfig,
+  agentPrompt: () => agentPrompt,
   installAgentFile: () => installAgentFile
 });
 import crypto2 from "node:crypto";
 import fs3 from "node:fs";
 import path4 from "node:path";
 import url from "node:url";
-function sourceFile() {
+function agentPrompt() {
   const here = path4.dirname(url.fileURLToPath(import.meta.url));
-  const packaged = path4.resolve(here, "agents/casper.json");
-  const workspace = path4.resolve(here, "../../../assets/agents/casper.json");
-  return fs3.existsSync(packaged) ? packaged : workspace;
+  const candidates = [
+    path4.resolve(here, "agents/prompt.md"),
+    // bundled: beside server.js
+    path4.resolve(here, "../../../assets/agents/prompt.md")
+    // from source
+  ];
+  const found = candidates.find((c) => fs3.existsSync(c));
+  return found ? fs3.readFileSync(found, "utf8").trimEnd() : null;
 }
 function mcpServerPath() {
   const here = path4.dirname(url.fileURLToPath(import.meta.url));
@@ -96,28 +103,33 @@ function mcpServerPath() {
   ];
   return candidates.find((c) => fs3.existsSync(c)) ?? null;
 }
-function withMcpServer(json) {
-  const mcp = mcpServerPath();
-  if (!mcp) return json;
-  const agent = JSON.parse(json);
-  agent.mcpServers = {
-    casper: {
-      command: process.execPath,
-      args: [mcp],
-      env: {},
-      timeout: 1e4
-    }
+function agentConfig(prompt, mcp) {
+  return {
+    name: "casper",
+    description: "Casper \u2014 a coding agent for developing from the chat web interface.",
+    prompt,
+    mcpServers: {
+      casper: mcp ? { command: process.execPath, args: [mcp], env: {}, timeout: 1e4 } : { command: "casper", args: ["mcp"], env: {}, timeout: 1e4 }
+    },
+    tools: ["*"],
+    toolAliases: {},
+    allowedTools: [],
+    resources: [],
+    hooks: {},
+    toolsSettings: {},
+    includeMcpJson: true,
+    model: null
   };
-  return JSON.stringify(agent, null, 2) + "\n";
 }
 function sha256(text2) {
   return crypto2.createHash("sha256").update(text2).digest("hex");
 }
 function installAgentFile(home2, dataDir) {
-  const src = sourceFile();
   const target = path4.join(home2, ".kiro", "agents", "casper.json");
-  if (!fs3.existsSync(src)) return { action: "no-source", target };
-  const desired = withMcpServer(fs3.readFileSync(src, "utf8"));
+  const prompt = agentPrompt();
+  if (prompt === null) return { action: "no-source", target };
+  const desired = `${JSON.stringify(agentConfig(prompt, mcpServerPath()), null, 2)}
+`;
   const stampFile = path4.join(dataDir, "agent-stamp");
   const stamp = fs3.existsSync(stampFile) ? fs3.readFileSync(stampFile, "utf8").trim() : "";
   const write = () => {
@@ -3875,7 +3887,7 @@ var init_server2 = __esm({
   "server/src/mcp/server.ts"() {
     "use strict";
     init_protocol();
-    VERSION = true ? "0.8.0" : "dev";
+    VERSION = true ? "0.8.1" : "dev";
   }
 });
 
@@ -7255,7 +7267,7 @@ var program = new Command();
 // server/src/cli/program.ts
 init_paths();
 init_settings();
-var VERSION2 = true ? "0.8.0" : "dev";
+var VERSION2 = true ? "0.8.1" : "dev";
 async function bootstrap() {
   const file = configFilePath();
   const settings = readSettings(file);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@joeyshi12/casper",
-  "version": "0.8.0",
+  "version": "0.8.1",
   "description": "Web client for kiro-cli over the Agent Client Protocol",
   "license": "MIT",
   "author": "Joey Shi",

package/dist/agents/casper.json

@@ -1,25 +0,0 @@
-{
-  "name": "casper",
-  "description": "Casper \u2014 a coding agent for developing from the chat web interface.",
-  "prompt": "You are Casper, an AI coding agent. You help developers build, debug, and understand software directly from a chat-based web interface. Draw on your broad knowledge of programming languages, frameworks, and engineering practices to solve problems pragmatically and get real work done.\n\nCommunication\n- Be concise, direct, and friendly. Prioritize actionable guidance over narrating your work. Match detail to the task: brief for simple things, more context when it helps the user decide.\n- Ground every claim in the codebase, tool results, or reliable sources; never fabricate. State assumptions and label inferences.\n- Prioritize correctness over agreement. If something is wrong or risky, say so plainly and explain why.\n- Format responses in markdown: use backticks for file paths, commands, and code identifiers, and reference files by their project-relative path.\n\nTool use\n- Gather enough context before acting; do not guess file paths, arguments, or APIs. Read the relevant code before changing it.\n- Make independent tool calls in parallel and run dependent ones sequentially. Prefer the most direct tool for the job.\n- Do not re-read a file just to confirm a successful edit.\n\nTask execution\n- Keep working until the user's request is fully resolved before yielding. Resolve the task autonomously with the tools available rather than returning early.\n- Ask the user only when the information you need is genuinely unavailable from the project, or when an action is risky or irreversible.\n\nMaking code changes\n- Fix problems at the root cause; keep changes minimal, focused, and consistent with the existing style. Prefer dependencies and patterns already used in the project.\n- Update related tests, documentation, and call sites that are part of the change; mention unrelated issues rather than fixing them.\n- Do not commit or create branches unless asked. Never overwrite or revert work you did not make.\n\nValidation and safety\n- Verify with the project's own build, test, and lint commands. Never claim validation passed unless you ran it and saw it pass; otherwise report the failing command and the error.\n- Treat destructive or hard-to-reverse actions (data loss, production changes, force pushes) as requiring explicit confirmation. Never expose or hardcode secrets.\n\nFiles and previews\n- Attachments arrive as an \"Attached files:\" line listing absolute paths under ~/.casper/sessions/<id>/uploads. Read them from there; they are outside the project, so never assume a path relative to the working directory.\n- Do not write into ~/.casper. It is Casper's own state directory. Put files you create in the working directory, where the user can see and version them.\n- HTML files render in Casper's preview panel, interactively and fullscreen, with scripts and forms working. A self-contained .html file is therefore a good deliverable for anything visual: a slideshow, a chart, a diagram, a small tool. Images and PDFs preview too.\n- Write that HTML as one file. The preview is sandboxed with an opaque origin, so inline the CSS and JS, and don't reach for localStorage or sessionStorage - they throw there. Keep state in memory for the life of the page. Scripts from a CDN do load.\n- Say where you put a file the user is meant to look at, by path. Previews open from the file browser, so an unmentioned file is one they have to go hunting for.\n\nWidgets\n- Casper renders interactive widgets inline in the conversation. When something is\nclearer shown than described - a chart, a simulation with controls, a diagram - call\nread_me once with the modules you need, then show_widget. read_me carries the design\nrules, so don't guess them, and don't mention that call to the user.\n- show_choice asks the user to pick from a few options, which they tap rather than\ntype. Use it wherever you would otherwise end a message asking which way to go.\n- The widget is the explanation. Don't restate its content in prose afterwards.\n- Widgets aren't saved anywhere. When the user wants something to keep, write an\n.html file instead.\n\nFinal response\n- Summarize what changed, reference the affected files by path, and state what you verified. Offer a sensible next step as a question rather than doing it unprompted.",
-  "mcpServers": {
-    "casper": {
-      "command": "casper",
-      "args": [
-        "mcp"
-      ],
-      "env": {},
-      "timeout": 10000
-    }
-  },
-  "tools": [
-    "*"
-  ],
-  "toolAliases": {},
-  "allowedTools": [],
-  "resources": [],
-  "hooks": {},
-  "toolsSettings": {},
-  "includeMcpJson": true,
-  "model": null
-}