agent-state-machine 2.0.2 → 2.0.4

package/README.md

@@ -44,11 +44,11 @@ Requirements: Node.js >= 16.
 ```bash
 state-machine --setup <workflow-name>
 state-machine run <workflow-name>
+state-machine run <workflow-name> -reset
+state-machine run <workflow-name> -reset-hard
 
 
 state-machine history <workflow-name> [limit]
-state-machine reset <workflow-name> (clears memory/state)
-state-machine reset-hard <workflow-name> (clears everything: history/interactions/memory)
 ```
 
 Workflows live in:
@@ -140,7 +140,7 @@ export default async function() {
 
 `state-machine run` restarts your workflow from the top, loading the persisted state.
 
-If the workflow needs human input, it will **block inline** in the terminal. You’ll be told which `interactions/<slug>.md` file to edit; after you fill it in, press `y` in the same terminal session to continue.
+If the workflow needs human input, it will **block inline** in the terminal. You can answer in the terminal, edit `interactions/<slug>.md`, or respond in the browser.
 
 If the process is interrupted, running `state-machine run <workflow-name>` again will continue execution (assuming your workflow uses `memory` to skip completed steps).
 
@@ -172,8 +172,8 @@ memory.count = (memory.count || 0) + 1;
 
 Gets user input.
 
-- In a TTY, it prompts in the terminal.
-- Otherwise it creates `interactions/<slug>.md` and blocks until you confirm in the terminal.
+- In a TTY, it prompts in the terminal (or via the browser when remote follow is enabled).
+- Otherwise it creates `interactions/<slug>.md` and blocks until you confirm in the terminal (or respond in the browser).
 
 ```js
 const repo = await initialPrompt('What repo should I work on?', { slug: 'repo' });
@@ -298,7 +298,7 @@ export const config = {
 };
 ```
 
-The runtime captures the fully-built prompt in `state/history.jsonl`, viewable in the browser with live updates when running with the `--local` flag or via the remote URL.
+The runtime captures the fully-built prompt in `state/history.jsonl`, viewable in the browser with live updates when running with the `--local` flag or via the remote URL. Remote follow links persist across runs (stored in `workflow.js` config) unless you pass `-n`/`--new` to regenerate.
 
 ---
 

package/bin/cli.js

@@ -361,14 +361,18 @@ async function runOrResume(
   try {
     await runtime.runWorkflow(workflowUrl);
   } finally {
-    // Cleanup
-    if (remoteUrl) {
+    // Keep local server alive after run so the session remains accessible.
+    if (!useLocalServer && remoteUrl) {
       await runtime.disableRemote();
     }
-    if (localServer) {
+    if (!useLocalServer && localServer) {
       localServer.close();
     }
   }
+
+  if (useLocalServer) {
+    console.log('Local server still running for follow session. Press Ctrl+C to stop.');
+  }
 }
 
 async function main() {

package/lib/runtime/runtime.js

@@ -533,7 +533,7 @@ export class WorkflowRuntime {
     // Send existing history if connected
     if (this.remoteClient.connected) {
       const history = this.loadHistory();
-      this.remoteClient.sendSessionInit(history);
+      await this.remoteClient.sendSessionInit(history);
     }
 
     this.remoteEnabled = true;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-state-machine",
-  "version": "2.0.2",
+  "version": "2.0.4",
   "type": "module",
   "description": "A workflow orchestrator for running agents and scripts in sequence with state management",
   "main": "lib/index.js",

package/vercel-server/api/events/[token].js

@@ -59,9 +59,21 @@ export default async function handler(req, res) {
     const eventsListKey = `${KEYS.events(token)}:list`;
     let lastEventIndex = 0;
 
-    // Get current list length to start from
+    // If history is empty, seed from the event list to catch early events.
     const currentLength = await redis.llen(eventsListKey);
-    lastEventIndex = currentLength;
+    // if (history.length === 0 && currentLength > 0) {
+    //   const existingEvents = await redis.lrange(eventsListKey, 0, -1);
+    //   const entries = existingEvents
+    //     .map((event) => (typeof event === 'object' ? event : JSON.parse(event)))
+    //     .filter(Boolean);
+    //   res.write(`data: ${JSON.stringify({
+    //     type: 'history',
+    //     entries,
+    //   })}\n\n`);
+    //   lastEventIndex = currentLength;
+    // } else {
+    //   lastEventIndex = currentLength;
+    // }
 
     const pollInterval = setInterval(async () => {
       try {

package/vercel-server/api/ws/cli.js

@@ -59,6 +59,9 @@ async function handlePost(req, res) {
         // Create session
         await createSession(sessionToken, { workflowName, cliConnected: true });
 
+        // Replace any existing history and event stream with the provided snapshot
+        await redis.del(KEYS.history(sessionToken), `${KEYS.events(sessionToken)}:list`);
+
         // Store initial history
         if (history && history.length > 0) {
           await addHistoryEvents(sessionToken, history);