@joeyshi12/casper 0.11.1 → 0.13.0

package/README.md

@@ -25,7 +25,7 @@ exactly what it missed.
 - **Widgets**: the agent calls a `show_widget` tool over MCP and the result renders
   inline as a live page. Charts, simulations, animated diagrams. Sandboxed, and they
   can send a message back.
-- **Observability** for credits spent, context-window usage and turn duration.
+- **Context-window usage** shown live, with one tap to compact.
 - **PWA** that installs to a home screen and reconnects when the network returns.
 
 ## Install
@@ -133,6 +133,9 @@ Casper launches kiro with `--trust-all-tools` so unattended runs never block on
 approvals. The agent can run commands and write files without asking, so treat
 access to Casper as equivalent to a shell on the machine.
 
+`CASPER_FILE_ROOT` is the only limit on what the file endpoints will read, and it defaults
+to everything the server can read. Narrow it if that matters to you.
+
 The token is 24 random bytes, generated for you and exchanged at login for a
 per-device cookie; only its hash is stored. Comparison is constant-time, and
 `/api/login` allows ten failures per quarter hour per address before answering 429.

package/dist/agents/prompt.txt

@@ -35,7 +35,7 @@ Ask first before anything destructive or hard to reverse, such as deleting data,
 </working_in_code>
 
 <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.
+Attachments arrive as an "Attached files:" line listing absolute paths under ~/.casper/chats/<chat 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 person 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, a study sheet. Images and PDFs preview too. Give them some character rather than defaulting to the same centred card on a white background every time.
 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.

package/dist/mcp.js

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