feat(cli): add read-only basou portfolio listing command#173
Merged
Conversation
An agent oriented in one project had no headless way to discover where a
sibling project lives: the portfolio was reachable only via the
`basou view --portfolio` localhost GUI (unreachable in a non-interactive
session) or by reading ~/.basou/portfolio.yaml by hand. So an agent
structurally falls back to globbing the filesystem even though basou already
holds the mapping. `basou portfolio` closes that gap, and fixes the
"unknown command 'portfolio'" foot-gun (the name an agent naturally reaches
for).
- New top-level `basou portfolio` (read-only): lists each registered planning
master's label + path, and whether it exists / owns a `.basou/` store.
- `--json` for machine consumption (stable, minimal shape:
`{ configPath, workspaces: [{ label, path, exists, initialized }] }`).
- Reuses `loadPortfolioConfig`; probes only existence + `.basou` presence.
Deliberately does NOT run the `basou view --check` redundancy/footprint
safety preflight; that stays its own surface.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
takashi-matsuyama
force-pushed
the
feat/portfolio-list-command
branch
from
July 14, 2026 15:36
049122b to
be33a48
Compare
Adversarial review follow-ups on `basou portfolio`: - A1: `initialized` now requires `.basou` to be a DIRECTORY (statSync isDirectory), matching the canonical `hasBasouStore` probe, so a stray regular file named `.basou` is not mis-reported as an initialized master. - A2: pin the `--json` output to single-line minified JSON (no pretty-print), so line-oriented consumers stay stable. - A3: cover the wired `runPortfolioList` entry: a missing config renders the error and sets exitCode 1. Design-reversal findings B1-B7 were reviewed and kept as-is (operator call): the read-only scope boundary vs `basou view --check` and the exit-code contract consistent with `basou view --portfolio` stand. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jul 14, 2026
Merged
takashi-matsuyama
added a commit
that referenced
this pull request
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
An agent oriented in one project has no headless way to discover where a sibling project lives. The portfolio is reachable only via:
basou view --portfoliolocalhost GUI (unreachable in a non-interactive/headless session — an agent can't open a browser), or~/.basou/portfolio.yamlby hand.So an agent structurally falls back to globbing the raw filesystem (
ls ~/projects/*<name>*) even though basou already holds the label→path mapping. This also fixes theerror: unknown command 'portfolio'foot-gun —portfoliois the exact name an agent reaches for.(Motivation surfaced from a real session where an agent globbed the filesystem to locate a sibling project while
~/.basou/portfolio.yamlalready had the answer.)What
basou portfolio(read-only): lists each registered planning master'slabel+path, and whether itexists/ owns a.basou/store (initialized).--jsonfor machine consumption. Stable, minimal shape (part of the CLI contract):{ "configPath": "…", "workspaces": [ { "label": "takuhon", "path": "/…/takuhon-planning", "exists": true, "initialized": true } ] }loadPortfolioConfig; probes only existence +.basoupresence. Deliberately does NOT run thebasou view --checkredundancy/footprint safety preflight — that stays its own surface.exists:false, initialized:falserather than throwing; a missing/malformed config propagatesloadPortfolioConfig's existing user-facing error (exit 1), consistent withbasou view --portfolio.Scope / non-goals
~/.basou/portfolio.yamlformat.basou view --portfolio(GUI) orbasou view --check(safety preflight) — it is the lightweight discovery counterpart.Tests
packages/cli/src/commands/portfolio.test.ts(label/path/exists/initialized resolution, stale-entry guard that never probes.basou,--jsonshape, human render markers, missing-config error).program.test.tscommand-tree assertion updated to includeportfolio.lint:lang✓ (English-only), build ✓, andbasou portfolio/--jsonverified end-to-end against the real 12-workspace config.🤖 Generated with Claude Code