nebi-sessionslisted
Install: claude install-skill romanized/nebi-skill
# Context and sessions: protect the thinker, know where we are
The active harness's core §0 override always wins. This is the default posture when you are deciding alone.
## Session start — survey before acting
At the start of substantial work, use the current request, the selected task checkpoint when resuming, and the hot files or diff. Simple questions need no state ceremony. Dispatch a scout only when the reading is genuinely heavy, independent, and worth isolating. For a run long enough to compact, keep its task list in the checkpoint or a file, tick items as they finish, and read that list rather than the scrollback.
## Select context by project and task
- The shared store is `~/.agents/nebi/projects/<project-id>/tasks/<task-id>/`. Git common-directory identity groups a repository and its worktrees; the checkpoint retains its checkout/branch. Different clones and same-named folders stay separate. Without Git, the explicit working directory identifies the project.
- The startup hook supplies this project's context and native session id. Use `node ~/.codex/nebi/context.mjs show --cwd <directory> --session <id>` in Codex, or `~/.claude/nebi/context.mjs` in Claude Code. `show` is read-only and returns the selected checkpoint, revision, handoff directory, Git differences and up to five other unfinished tasks in this project.
- A new session gets a separate task by default. For a resume, match the user's intent to the task's goal and evidence; use `select --cwd <director