99 lines
4.6 KiB
Markdown
99 lines
4.6 KiB
Markdown
---
|
|
type: session
|
|
id: session.paperclip-harness.rich-discovery-config-2026-11-12-06-19-59
|
|
title: Rich discovery: .config 2026-11-12 06:19:59
|
|
status: active
|
|
source_of_truth: false
|
|
freshness: current
|
|
last_reviewed: 2026-11-12
|
|
tags:
|
|
- pack/paperclip-harness
|
|
- agent-memory/session
|
|
- autolearn
|
|
- rich-discovery
|
|
- repo/config
|
|
---
|
|
|
|
# Rich discovery: .config 2026-11-12 06:19:59
|
|
|
|
Sanitized rich discovery snapshot captured automatically from the completed turn.
|
|
|
|
|
|
## Source paths observed
|
|
|
|
- `paperclip-harness/tui/paperclip`
|
|
- `home/sam/SECURITY`
|
|
- `HOME/.local/share/paperclip-harness/bin/office`
|
|
- `home/sam/SECURITY/.harness/harness.toml`
|
|
- `nix/store/m15fsh578q4yplc2hi12gp5xsyn6zkq2-tuios-0.12.1/bin/tuios`
|
|
- `etc/profiles/per-user/sam/bin/tuios`
|
|
- `home/sam/.config/paperclip-harness/projects.toml`
|
|
- `home/sam/SECURITY/.harness/check.sh`
|
|
- `home/sam/SECURITY/.harness/NOTES.md`
|
|
- `.config/environment.d/10-secrets.conf`
|
|
- `.local/share/paperclip-harness/bin`
|
|
|
|
## Final answer snapshot
|
|
|
|
Fixed, and your `security` project is now running.
|
|
|
|
## What the error was
|
|
|
|
Two things, and the first hid the second.
|
|
|
|
**1. The key is not in your shell on `.27`.** `PAPERCLIP_BOARD_KEY` lives in `~/.config/environment.d/10-secrets.conf`, which systemd's user manager reads. On `.13` the session inherits it; on `.27` your terminal is started by the desktop session, which does not import `environment.d`. So the file was right there and the variable was empty.
|
|
|
|
**2. Even with the key, `office` on `.27` was aiming at the wrong machine.** The default address was `http://127.0.0.1:3100`, and Paperclip runs on `.13`. `.27` can reach it — I checked, 200 — but nothing was asking that address.
|
|
|
|
Both are fixed in the code, on the Python commands and in the Go program, so it works from a shell and from inside a pane:
|
|
|
|
- the key, the company id and the API address are read from `~/.config/environment.d/*.conf` when the environment does not have them (read only; never printed);
|
|
- if `PAPERCLIP_API_URL` is not set and `127.0.0.1:3100` does not answer, the address becomes `http://192.168.20.13:3100`.
|
|
|
|
## A third problem your command would have hit
|
|
|
|
`~/SECURITY` is **not a git repository**, and `--new` always created a project with a branch per task in a worktree. A worktree needs a repository, so every run on that project would have failed. `--new` now checks, and for a folder that is not a repository it creates a `local_path` project: the folder stays in place and a task changes the files directly. It says so when it does that.
|
|
|
|
## It is created and running
|
|
|
|
```
|
|
project security 8b33e222-8b62-40a2-950d-dbc9a3a2ffcd
|
|
source local_path cwd /home/sam/SECURITY
|
|
policy none (no worktrees: not a git repository)
|
|
session security on .27, 8 panes
|
|
panes board · work · agents · reply · new · project · repair = harness
|
|
shell = a shell
|
|
```
|
|
|
|
Attach with `tuios attach security` on `.27`.
|
|
|
|
If you would rather have a branch per task for that folder, `git init` it and re-run `office ~/SECURITY --project security`; the project keeps the folder but you would need a new one to get the worktree policy, because the policy is set when the project is created.
|
|
|
|
## Two things I noticed on `.27` while doing this
|
|
|
|
- **`tuios.service` is in `activating (auto-restart)`** — the unit keeps failing to start, while a manually started daemon (pid 1603888) is what your sessions actually live on. That is why your sessions exist at all. After a reboot the manual daemon will not be there, so this is worth fixing before you rely on `.27` surviving a restart.
|
|
- The `.27` rebuild for `~/.local/bin` on `PATH` clearly took effect, since `office` resolved by name. **`.51` still needs its rebuild** if you have not done it yet:
|
|
|
|
```sh
|
|
sudo nixos-rebuild switch --flake /etc/nixos#sam-thinkpad
|
|
```
|
|
|
|
## Committed
|
|
|
|
`paperclip-harness` → `55085ba`. The updated commands are also copied to `.27` and `.51` at `~/.local/share/paperclip-harness/bin/`, with `--help` working on both.
|
|
|
|
## Evidence
|
|
|
|
- Confidence: 86%
|
|
- Reason: Preserve full sanitized discovery detail from a rich investigation turn
|
|
|
|
## Related
|
|
|
|
- [[packs/paperclip-harness/00-system/pi-agent/memory-manifest|Memory Manifest]]
|
|
|
|
## Related learned memories <!-- same-turn-2026-11-12 06:19:59 -->
|
|
|
|
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-config-2026-11-12-06-19-59|Rich discovery: .config 2026-11-12 06:19:59]]
|
|
- context: [[packs/paperclip-harness/20-context/config|.config]]
|
|
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|.config repository structure and configuration patterns]]
|