Skip to content

docs(gentle): agent-gentle deploy and built-in MCP for brains #103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
barbatdev merged 2 commits into from
Oct 31, 2026
Merged

docs(gentle): agent-gentle deploy and built-in MCP for brains #103

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cd8989c
docs(gentle): record agent-gentle deploy and built-in MCP for brains
barbatdev Oct 31, 2026
1dc792b
docs(gentle): record RefactorIA theme on agent-gentle
barbatdev Oct 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions docs/gentle-official-migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -320,3 +320,38 @@ Primera corrida: el paso 1 falló en la limpieza de `conductor` porque intentó
- Paso 6: `profiles.json` ya era idéntico al backup tras la copia de `setup`; se instaló `refactoria.json` y se fijó el theme.
- Paso 7: `gentle-ai 4.3.2-0.20261031025914-c60a4b6d5675` compilado desde `main`, instalado solo para Claude Code (25/25 checks). La pregunta del allowlist de Engram se salta sola en modo no interactivo.
- Paso 9: `gs`, `gentle-shell`, `gentle-ai` y `codegraph` resuelven en `~/.local/bin`, y `go` en `/opt/homebrew/bin`.

## MCP (brains) en el home aislado

**Pi 1.4.0 trae MCP incorporado: lee los servidores de `mcp.json` en el home del agente.** Para Gentle Shell ese archivo es `~/.gentle-shell/agent/mcp.json`. **No instalar `pi-mcp-adapter`**: Gentle AI lo considera retirado y lo borra en cada `gentle-shell setup` (`internal/agents/pi/adapter.go`), y mientras está instalado tapa el MCP incorporado.

Procedimiento aplicado el 2026-10-31 en la Mac, `agent-dev` y `agent-gentle`, sin abrir el archivo:

```bash
cp -p ~/.config/mcp/mcp.json ~/.gentle-shell/agent/mcp.json # no pisar uno existente
chmod 600 ~/.gentle-shell/agent/mcp.json
gentle-shell --isolated remove npm:pi-mcp-adapter # solo si estaba instalado
gentle-shell --isolated mcp list # mirar solo nombres y estado
```

Resultado en los tres equipos: `work-brain` (26 tools), `life-brain` (14) y `second-brain` (17) `connected`. En `agent-dev` la misma configuración incluye un servidor `codegraph` que figura `failed`; pendiente de revisar (probable PATH).

## agent-gentle (workshop)

`agent-gentle` es dogfooding: Shell corre desde el clon `~/dev/gentle/gentle-shell` y `gs` es el `bin/gs` de workshop, con sus accesorios (`gs issue`, `gs pr`, `gs review`, `gs new`, `gs base`, `gs ls`, `gs done`). **No se usa el instalador oficial ni `gs-official`**: borrarían esos accesorios. Spec y log completos: [`odd/tasks/agent-gentle-official-home.md`](../odd/tasks/agent-gentle-official-home.md).

| Paso (2026-10-31) | Resultado |
|---|---|
| Backup previo | Backup diario cifrado al NAS (`agent-gentle-backup.timer`) de las 03:44 con `Result=success`. |
| `bin/gs` (PR #101, #102) | Arranques con `--isolated` y `--package-root`, nunca `--link`; `gs sync` workshop sincroniza solo Claude Code y corre `gentle-shell --isolated setup`. |
| Skills | 12 skills `cortex-*` copiados de `~/.pi/agent/skills` a `~/.agents/skills` (Pi los lee ahí con cualquier home). Originales intactos. |
| Wrapper `~/.local/bin/gentle-shell` | Sin `GENTLE_SHELL_PI=~/.pi/agent/bin/pi`; mantiene `GENTLE_SHELL_NO_AUTO_SETUP=1`. |
| `gs sync` real | `gentle-ai sync` ok, `gentle-shell setup (isolated home)` ok, compat `v9` OK. Shell `4.5.1`, Gentle AI `c60a4b6d5675`, Engram `7cf4ed29b6f9`. |
| Pi legacy | `~/.pi/agent/bin/pi` y el symlink `~/.local/bin/pi` movidos a `~/gentle-workshop-retirement.ufAbAo`, junto con el wrapper original. |
| Worktrees viejos | Un launcher anterior (p. ej. `gentle-shell 3.7.0` en `pr-1520`) busca `pi` en el `PATH`: `~/.local/bin/pi` apunta ahora al Pi del clon `main` (`~/dev/gentle/gentle-shell/node_modules/.bin/pi`). Los launchers nuevos usan el Pi de su propio worktree. |
| Theme RefactorIA | `pi/themes/refactoria.json` del repo (idéntico al del home legacy) copiado a `~/.gentle-shell/agent/themes/` y `"theme": "refactoria"` en `~/.gentle-shell/agent/settings.json`; settings previo en el backup. `gentle-shell setup` conserva el theme elegido. |
| Verificación | `pi` legacy ausente; `gs --version` fuera de un clon y desde un worktree: home `isolated`; brains `connected`. |

**Se conservan a propósito:** `~/.pi/gentle-ai/dev-binary.json` y `channel.json` (estado de instalación que el lanzador oficial lee ahí), worktrees con cambios sin commitear, Engram y Herdr.

**Pendiente:** el paso de dotfiles de `gs sync` usa `CORTEX_DOTFILES_DIR=~/.local/share/cortex-dotfiles`, un clon distinto del que usa `gs` (`~/dev/barbatdev/cortex/cortex-dotfiles`), y lo saltea porque tiene cambios locales. Unificar o decidir cuál queda.
3 changes: 2 additions & 1 deletion odd/tasks/agent-gentle-official-home.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Shell keeps running from the gentle-shell clone; only the home, Pi runtime and G

- T1 (S2-S6) worker + parent fixes: change `bin/gs` + tests + docs. Done. Commit: e89c3d1
- T3 (S8) worker: workshop sync scope + isolated setup. Done. Commit: see branch feat/agent-gentle-sync-scope
- T2 (S7) parent: deploy and verify on agent-gentle. Commit: n/a (host)
- T2 (S7) parent: deploy and verify on agent-gentle. Done 2026-10-31 (see docs/gentle-official-migration.md#agent-gentle-workshop). Commit: n/a (host)

## Log

Expand All @@ -28,3 +28,4 @@ Shell keeps running from the gentle-shell clone; only the home, Pi runtime and G
- L4 Parent review: removed the isolated-settings gentle-pi/gentle-engram warning; on agent-gentle the official Shell declares both there (gentle-engram is its required companion), so it would fire on every sync. Skill cortex-maintainer-delivery exists only in ~/.pi/agent/skills on agent-gentle; T2 must expose it to the isolated home before retiring legacy.
- L5 Verifier FAIL on S4: the launcher reads dev-binary.json from ~/.pi/gentle-ai, not the isolated config home (confirmed on agent-gentle clone 14f44d11c, lib/gentle-ai-binary.ts:218). S4 rewritten: keep writing ~/.pi/gentle-ai/dev-binary.json; T1 reopened and fixed.
- L6 User asked whether gs sync also runs gentle-ai sync and whether gentle-shell has its own: "en el gs sync metimos también un gentle-ai sync? porque eso es lo que esta documentado en el proceso de actualizacion. Hay que revisar si gentle-shell no tiene algo de esto también". Finding: workshop runs bare `gentle-ai sync`; installed_agents on agent-gentle = claude-code, opencode, pi, so it keeps syncing the legacy ~/.pi/agent (gentle-shell README: `gentle-ai sync` is Path B, gentle-pi inside an existing pi) and never the isolated home; `gentle-shell setup` re-provisions the isolated home; the agent-gentle wrapper sets GENTLE_SHELL_NO_AUTO_SETUP=1. User decision on agents: "solo claude code".
- L7 Deploy findings: Pi 1.4.0 has built-in MCP reading <agentDir>/mcp.json; gentle-ai retires pi-mcp-adapter on setup, so brains moved to ~/.gentle-shell/agent/mcp.json on Mac, agent-dev and agent-gentle and the adapter was removed. Old worktree launchers look for pi on PATH: ~/.local/bin/pi now points to the main clone Pi.
Loading