#Claude bots using LLM instead of real memory.md, lost all API intergration enhancements on agents.

1 messages · Page 2 of 1

craggy lotusBOT
#

Perfect — that 404 spam was 100% “bad token”, so rotating/fixing it tracks.

If you want to sanity-check it’s fully healthy now:

openclaw channels status --probe
openclaw pairing list telegram

And if this fixed it, please mark the solution message (right‑click → Apps → ✅ Mark Solution) so Answer Overflow indexes it.

brazen hemlock
#

yeah no it works! that key rotation was legit, axiom did that super fast and quick. Anyways, how can i make sure a gitrepo is safe to download? To o bash in terminal w code or what? Can't download the huge zip files, and don't wanna do something wrong.

#

Also if i get docker will these agen't work better? i can't just put Axiom in the docker and then the other 2 are pretty much safe because they're just getting nodes from axiom, so if he's compromised he's lowkey safe as well

craggy lotusBOT
#

Making sure a git repo is “safe” to download (without huge zips)

Downloading/cloning is usually fine — running stuff from the repo is the risky part.

A pretty safe workflow:

  1. Clone minimally (faster + avoids big blobs)
GIT_LFS_SKIP_SMUDGE=1 git clone --depth 1 --filter=blob:none <repo-url>
  1. Inspect before executing anything
    Look for “auto-run” / install hooks:
  • package.json (scripts, esp. postinstall)
  • Dockerfile, Makefile, install*.sh
  • .github/workflows/*

Quick red-flag grep:

# 
grep -RInE "curl\\s|wget\\s|powershell|Invoke-WebRequest|sudo\\s|rm\\s+-rf|chmod\\s+\\+s|ssh\\s|nc\\s" .
  1. If it’s Node-based, install deps without running scripts first
npm ci --ignore-scripts
# or pnpm install --ignore-scripts
  1. Only then run the normal setup, ideally in an isolated environment (see below).

If you drop the repo URL (just the GitHub link), I can tell you what files to inspect first.

“If I get Docker will my agents work better / be safer?”

#

Docker can help stability and isolation, but it’s not a magic “safe” switch.

Key security model point: if “Axiom” is your central gateway/brain and it’s compromised, it can still:

  • read any secrets you mounted into it (.env, ~/.openclaw, API keys)
  • instruct other nodes to run things if those nodes allow it (that’s what exec approvals/allowlists are for)

So the “put Axiom in Docker and the other 2 are safe” idea is only true if you also lock down the other 2:

  • Don’t mount extra secrets into the container unless needed.
  • Keep node exec locked down (allowlist mode + approvals). Nodes can be configured so system.run requires approval / only allows specific commands.
    Docs: https://docs.openclaw.ai/nodes/troubleshooting (Pairing vs approvals)

What Docker does help with:

  • running untrusted repos in a throwaway environment (best use case)
  • preventing installs from polluting your host OS
  • making “reset to clean state” easy
#

Best practice: use Docker/VM for running unknown code, and keep your real OpenClaw gateway/node env minimal + least-privilege.

If you tell me what kind of repo it is (Node/Python/Go) and where you plan to run it (Mac/VPS), I’ll give you a tight “safe run” command set for that stack.

#

git clone itself is usually the safe part — the risky part is running whatever the repo tells you to run (curl | bash, npm install, make install, etc.). Here’s a good “don’t shoot yourself in the foot” flow.

Quick safety checklist (practical)

  1. Verify you’re cloning the right repo
  • check the GitHub org/user is the real one (not a typo-squat)
  • skim README + Issues (are people using it? any “this is compromised” reports?)
  1. Clone in a way that minimizes surprises (and size)
  • Don’t use --recurse-submodules unless you’ve reviewed it.
  • For huge repos / LFS blobs:
GIT_LFS_SKIP_SMUDGE=1 git clone --depth 1 --filter=blob:none <REPO_URL>

If you only need one folder, use sparse checkout:

# 
git clone --depth 1 --filter=blob:none --no-checkout <REPO_URL> repo
cd repo
git sparse-checkout init --cone
git sparse-checkout set path/you/need
git checkout
  1. Inspect before you run anything
    Look at:
  • package.json (scripts)
  • Makefile
  • Dockerfile
  • install*.sh
  • .github/workflows/* (what the project expects to run)

Quick red-flag search:

# 
grep -RInE "curl|wget|powershell|Invoke-WebRequest|sudo|rm -rf|chmod \+s|ssh|nc " .
  1. If it’s a Node project, install deps without running scripts first
    (NPM packages can run postinstall scripts.)
npm ci --ignore-scripts
# or: pnpm install --ignore-scripts

Then once you’ve reviewed package.json scripts + deps, run the normal install.

  1. Run it in isolation if you care about your machine
    Best practice: a throwaway Docker container / VM, no SSH keys, no .env secrets mounted.
#

Example:

docker run --rm -it -v "$PWD":/work -w /work node:22 bash

About curl | bash

Avoid it. If you must, do:

curl -fsSL <url> -o install.sh
less install.sh
bash -n install.sh
bash install.sh

If you drop the repo URL (just the GitHub link), I can tell you what to check specifically (LFS, install scripts, weird deps, etc.).

brazen hemlock
#

@craggy lotus

brazen hemlock
#

hello

brazen hemlock
#

@craggy lotus

#

my agent can't remember what his skills and or OG soul is

brazen hemlock
#

@craggy lotus

brazen hemlock
#

@craggy lotus