Repository navigation
Conversation
New recipe for deploying a personal OpenClaw AI assistant on the Engaging cluster using Apptainer/SLURM. Covers container build, setup wizard, agent testing, web dashboard via SSH tunnel, updates, and customization (data access, GPU, model switching, persistence). Based on https://github.com/qsimeon/openclaw-engaging Co-authored-by: Cursor <cursoragent@cursor.com>
lmilechin
requested changes
Feb 26, 2026
- Add prominent responsible-use and data-privacy warning (cloud LLM providers receive prompts and file contents) - Remove false "no data leaves the cluster" claim - Recommend scratch storage for ~/.openclaw/ to avoid filling home quota - Add API usage limits warning (potential account bans from heavy use) - Replace "how to disable sandboxing" with security-focused guidance on keeping sandboxing enabled and using --containall - Fix broken internal link to filesystems documentation Made-with: Cursor
The agent needs the internal sandbox off to run commands and manage files on the cluster. Reframe the Sandboxing section to explain why disabling is necessary while emphasizing --containall and minimal bind mounts as the real security boundary. Made-with: Cursor
- Storage: scratch as default, PI/group as option (with purge warning) - Replace sbatch+cat with start-gateway.sh for dashboard launch - Add responsible use & data privacy warning (top of doc) - Clarify sandboxing: Apptainer default vs --containall - Add API usage limits warning - Mention start-multi.sh, workspace init in Advanced Usage section Made-with: Cursor
Every ORCD user has ~/orcd/scratch — use this instead of the generic /orcd/scratch/$USER path. Also move read-only container clarification to top of sandboxing note for emphasis. Made-with: Cursor
Collaborator
Author
|
The |
- Add troubleshooting entries from fresh-user walkthrough: pairing code fix, token not auto-filling, ENOTDIR after symlink move, OOM during setup, and Node.js errors after updates - Bump interactive session memory from 1G to 4G (1G OOM kills the wizard) - Note that setup.sh applies HPC config after onboarding completes Made-with: Cursor
Collaborator
Author
|
Closing this fork-based PR in favor of a same-repo branch PR (now that I have push access). All commits carried over — new PR incoming. |
6 of 7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Based on the openclaw-engaging repo, which is a fork of upstream OpenClaw with Apptainer/SLURM additions for Engaging. Inspired by the DigitalOcean OpenClaw deployment but adapted for HPC constraints (ephemeral SLURM jobs, SSH tunneling, no systemd).
Files changed
docs/recipes/openclaw-engaging.md— new recipe (~425 lines)docs/images/openclaw/— two dashboard screenshotsmkdocs.yml— added nav entryChanges since review (addressing @lmilechin's feedback)
~/orcd/scratchfor~/.openclaw/— the state directory can grow large; added symlink instructions for scratch (default) and PI/group storage, with pointer to Storage and Filesystems docs--containallwith explicit bind mounts presented as stricter option per Chris Hill's recommendationsbatch+catwithstart-gateway.sh— 1-click launcher that submits the job, waits for startup, and prints the SSH tunnel command and dashboard URLstart-multi.shfor parallel gateway instances,orcd-workspace-init.shfor cluster-aware agentsChanges from fresh-user walkthrough (2026-03-12)
Full interactive walkthrough completed on the cluster with a clean slate. Fixes based on actual failure modes encountered:
--mem=1Gto--mem=4G(1G OOM kills the wizard)dangerouslyDisableDeviceAuth)ENOTDIRerror after moving.openclawto a symlinkTest plan