Skip to content
This repository was archived by the owner on Aug 21, 2026. It is now read-only.

Latest commit

 

History

History
171 lines (111 loc) · 4.03 KB

FIRST_5_MINUTES.md

File metadata and controls

171 lines (111 loc) · 4.03 KB

First five minutes — Willow 2.0

You will:

  1. Install
  2. Check health
  3. Start services
  4. (Optional) ping your desktop from your phone on the same Wi‑Fi

If something breaks, jump to If something fails at the bottom.


0) Install

Copy this block (Linux / macOS):

git clone https://github.com/rudi193-cmd/willow-2.0
cd willow-2.0
bash setup.sh --public

Agents without willow-config: read root ../willow.md or docs/CONTRACT.md for the public contract. Private operator context lives in willow-config — see docs/WILLOW_CONFIG.md.

Fleet operators: clone willow-config to ~/github/.willow, then run bash setup.sh so runtime config points at the private home while root willow.md stays public-safe.

Pre-commit hooks (ruff + path guard; mypy report on pre-push) — installed automatically by setup.sh. To reinstall:

source .venv-dev/bin/activate
pre-commit install
pre-commit install --hook-type pre-push

(setup.sh already installs editable willow + dev tools into .venv-dev.)

Use bash setup.sh without --public when private willow-config is present at ~/github/.willow. Manual lower-level path: python3 -m venv .venv-dev, pip install -r requirements.txt, pip install -e . --no-deps, pip install -r requirements-dev.txt, then python3 seed.py.

What you should see: setup steps scrolling, then your shell prompt back. No panic unless it stops with an error.

Default database name is willow_20. If you still have willow_19 from an old install, see CODE_DIFF_1.9_to_2.0.md.


1) Check status

./willow.sh fleet_status
./willow.sh status

Good: JSON or lines with [✓] on postgres, ollama, manifests.
Bad: degraded, not_connected, or a traceback — stop and fix before step 2.


2) Start Willow

./willow.sh start

Leave that terminal open if it streams logs. Open a second terminal for the next steps.


3) Optional — phone on same Wi‑Fi

Desktop

./willow.sh serve

Note the listening port (usually 7777) and ~/.willow/grove_token.

Phone (Termux)

pkg install python git
git clone https://github.com/rudi193-cmd/willow-2.0
cd willow-2.0
python3 seed.py --termux --skip-pg

Copy the desktop token:

echo "TOKEN" > ~/.willow/grove_token && chmod 600 ~/.willow/grove_token

Ask the desktop for status (replace IP):

bash ~/willow-2.0/willow.sh grove send 192.168.x.x:7777 status-all

Good: your desktop’s status printed on the phone.


Optional — IDE (Cursor / Claude Code)

Prefer the installer:

./willow.sh agents active <agent>
./willow.sh agents install <agent> --ide <cursor|claude|codex>
./willow.sh agents check --ide <cursor|claude|codex>

This writes MCP config for sap/unified_mcp.sh and links runtime settings for the chosen IDE. Manual .mcp.json setup is covered in IDE_INTEGRATION.md.


Optional — cloud model

Not required. Ollama is enough to start.

./willow.sh providers enable anthropic --key YOUR_KEY
./willow.sh providers list

Where your data lives

Path What
~/.willow/ Local Willow home
~/.willow/store/ SOIL collections
~/.willow/grove_token LAN pairing secret
Postgres willow_20 KB atoms (desktop)

Nothing uploads by default.


If something fails

Wrong folder

pwd && ls willow.sh seed.py

Postgres down

python3 seed.py

Phone cannot connect

  • Same Wi‑Fi as desktop
  • ./willow.sh serve still running
  • LAN IP, not 127.0.0.1
  • chmod 600 ~/.willow/grove_token

Tests or agents complain about identity

export WILLOW_AGENT_NAME=your_agent
export WILLOW_SAFE_ROOT=$HOME/SAFE/Applications

ΔΣ=42