sparkecoder 0.1.11 → 0.1.13

package/README.md

@@ -129,7 +129,8 @@ Create a `sparkecoder.config.json` file:
   },
   "server": {
     "port": 3141,
-    "host": "127.0.0.1"
+    "host": "127.0.0.1",
+    "publicUrl": "http://your-server:3141"
   }
 }
 ```
@@ -146,6 +147,7 @@ Create a `sparkecoder.config.json` file:
 | `context.autoSummarize` | Enable automatic summarization | `true` |
 | `server.port` | HTTP server port | `3141` |
 | `server.host` | HTTP server host | `127.0.0.1` |
+| `server.publicUrl` | Public URL for web UI (Docker/remote) | Auto-detected |
 
 ## Tools
 
@@ -308,6 +310,33 @@ When approval is required:
 | `SPARKECODER_PORT` | Override server port |
 | `DATABASE_PATH` | Override database path |
 
+## Docker / Remote Access
+
+When running SparkECoder in Docker or exposing it to remote clients, you need to configure the public URL so the web UI can connect to the API from the browser.
+
+### CLI Option
+
+```bash
+sparkecoder start --public-url http://your-server:3141
+```
+
+### Config File
+
+```json
+{
+  "server": {
+    "port": 3141,
+    "host": "0.0.0.0",
+    "publicUrl": "http://your-server:3141"
+  }
+}
+```
+
+**Notes:**
+- Set `host` to `0.0.0.0` to bind to all interfaces (required for Docker/remote access)
+- Set `publicUrl` to the URL the browser will use to reach the API
+- The web UI receives this URL at startup via `NEXT_PUBLIC_API_URL`
+
 ## Development
 
 ```bash

package/dist/agent/index.d.ts

@@ -1,6 +1,6 @@
 import 'ai';
 import '../schema-CkrIadxa.js';
-export { A as Agent, a as AgentOptions, b as AgentRunOptions, c as AgentStreamResult, C as ContextManager, d as buildSystemPrompt } from '../index-BeKylVnB.js';
+export { A as Agent, a as AgentOptions, b as AgentRunOptions, c as AgentStreamResult, C as ContextManager, d as buildSystemPrompt } from '../index-BzedNBK-.js';
 import '../bash-CGAqW7HR.js';
 import 'drizzle-orm/sqlite-core';
 import 'zod';

package/dist/agent/index.js

@@ -473,7 +473,10 @@ var SparkcoderConfigSchema = z.object({
   // Server configuration
   server: z.object({
     port: z.number().default(3141),
-    host: z.string().default("127.0.0.1")
+    host: z.string().default("127.0.0.1"),
+    // Public URL for web UI to connect to API (for Docker/remote access)
+    // If not set, defaults to http://{host}:{port}
+    publicUrl: z.string().url().optional()
   }).default({ port: 3141, host: "127.0.0.1" }),
   // Database path
   databasePath: z.string().optional().default("./sparkecoder.db")
@@ -1321,7 +1324,7 @@ import {
   createMessageConnection,
   StreamMessageReader,
   StreamMessageWriter
-} from "vscode-jsonrpc/node";
+} from "vscode-jsonrpc/node.js";
 import { pathToFileURL, fileURLToPath } from "url";
 import { readFile as readFile4 } from "fs/promises";
 import { existsSync as existsSync6 } from "fs";
@@ -2499,7 +2502,7 @@ Use this proactively after making code changes to catch errors early.
 ### Searching and Exploration
 ${searchInstructions}
 
-Follow these principles when designing and implementing software:
+###Follow these principles when designing and implementing software:
 
 1. **Modularity** \u2014 Write simple parts connected by clean interfaces
 2. **Clarity** \u2014 Clarity is better than cleverness
@@ -2519,6 +2522,16 @@ Follow these principles when designing and implementing software:
 16. **Diversity** \u2014 Distrust all claims for "one true way"
 17. **Extensibility** \u2014 Design for the future, because it will be here sooner than you think
 
+###Follow these ruls to be a good agent for the user:
+
+1. Understand first - Read relevant files before making any changes. Use search tools to explore the codebase and understand the existing patterns and structure.
+2. Plan for complexity - If the task involves 3+ steps or has meaningful trade-offs, create a todo list to track progress before implementing.
+3. Use the right tools - Have specialized tools for reading files, editing code, searching by pattern , running terminal commands, and more. Prefer these over raw shell commands.
+4. Work efficiently - When need to do multiple independent things (like reading several files), do them in parallel rather than one at a time.
+5. Be direct - Focus on technical accuracy rather than validation. If see issues with an approach or need clarification, say so.
+6. Verify my work - After making changes, check for linter errors and fix any introduced.
+7. Respect boundaries - Only commit code when explicitly asked, avoid creating unnecessary files, and don't make assumptions about things uncertain about.
+
 
 ### Communication
 - Explain your reasoning and approach