@pageai/ralph-loop 1.18.0 → 1.20.0

package/README.md

@@ -1,6 +1,6 @@
 # A Ralph Wiggum Loop implementation that works™
 
-[![@pageai/ralph-loop version](https://img.shields.io/npm/v/@pageai/ralph-loop?label=npm&style=flat)](https://github.com/pageai-pro/ralph-loop)
+[![@pageai/ralph-loop version](https://img.shields.io/npm/v/@pageai/ralph-loop?label=npm&style=flat)](https://www.npmjs.com/package/@pageai/ralph-loop)
 
 Ralph is a long-running AI agent loop. Ralph automates software development tasks by iteratively working through a task list until completion. This allows for long running agent loops, effectively enabling AI to code for days at a time.
 
@@ -34,6 +34,8 @@ This is an implementation that actually works, containing a hackable script so y
   - [Vitest configuration](#vitest-configuration)
   - [Running with a different agentic CLI](#running-with-a-different-agentic-cli)
   - [Starting from scratch](#starting-from-scratch)
+  - [Debugging](#debugging)
+- [How to inspect the sandbox and debug](#how-to-inspect-the-sandbox-and-debug)
 - [License](#license)
 
 ---------------------------------
@@ -266,7 +268,7 @@ To do so, you need to continue using the `prd-creator` skill to update the PRD a
 For example:
 
 ```
-I would like to expand the PRD / tasks with these tasks:
+I would like to expand the PRD. Use the prd-creator skill to create these tasks:
 
 - there is a bug in X that should be fixed by doing Y
 - create a new feature that implement Z
@@ -438,6 +440,38 @@ npm i @vitejs/plugin-react @testing-library/dom @testing-library/jest-dom @testi
 
 It is recommended that you add skills for your specific language and framework. See [skills.sh](https://skills.sh) to discover existing skills.
 
+### Debugging
+
+## How to inspect the sandbox and debug
+
+You might be wondering... if this is not a Docker container, how can you see what's going on inside Docker!?
+How to debug/install things?
+
+That's quite straightforward.
+
+You first need to run:
+
+```bash
+docker sandbox list
+```
+
+Note down the name of the sandbox, e.g. `claude-ralph-loop`.
+
+And then you can run bash into any of the sandboxes like so:
+```bash
+docker sandbox exec -it <sandbox-name> bash # e.g. docker sandbox exec -it claude-ralph-loop bash
+```
+
+And you have full control over the sandbox, just like a regular container. You can install packages, run commands, etc.
+
+You can also also run Claude Code inside the sandbox (make sure to navigate to the project directory first).
+
+```bash
+docker sandbox exec -it <sandbox-name> bash
+cd /path/to/your/project # this is the same path as the path in the root machine, e.g. /Users/your-username/Documents/your-project
+claude
+```
+
 ## License
 
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pageai/ralph-loop",
-  "version": "1.18.0",
+  "version": "1.20.0",
   "publishConfig": {
     "access": "public"
   },

package/ralph.sh

@@ -98,7 +98,7 @@ $(cat $SCRIPT_DIR/.agent/PROMPT.md)"
   export PROMPT_CONTENT
   export DOCKER_DEFAULT_PLATFORM=linux/amd64 # Needed for Playwright.
 
-  script -q "$OUTPUT_FILE" bash -c 'docker sandbox run claude . -- --model opus --output-format stream-json --verbose -p "$PROMPT_CONTENT"' >/dev/null 2>&1 &
+  script -q "$OUTPUT_FILE" bash -c 'docker sandbox run claude . -- --effort max --model opus --output-format stream-json --verbose -p "$PROMPT_CONTENT"' >/dev/null 2>&1 &
   AGENT_PID=$!
 
   # Track position in output file for incremental reading