Command-line client

Availability

The CLI currently lives in apps/cli and exposes the indielogs executable from the repository package. The repository does not declare a public npm release, so these instructions use the checked-out source rather than implying a published global install.

Configuration

export INDIELOGS_URL="https://your-indielogs-origin"
# Set INDIELOGS_TOKEN only for private or following-feed operations.
node apps/cli/bin/indielogs.mjs --help
node apps/cli/bin/indielogs.mjs operations
node apps/cli/bin/indielogs.mjs operations --details

Examples

node apps/cli/bin/indielogs.mjs feed --tab everyone --range week
node apps/cli/bin/indielogs.mjs call search.public '{"q":"founder tools"}'
node apps/cli/bin/indielogs.mjs list-projects
node apps/cli/bin/indielogs.mjs draft --project 123 --summary "Added a settings page"
node apps/cli/bin/indielogs.mjs publish DRAFT_UUID

Operational notes

• Public reads do not need a token; private operations and the following feed do.
• The CLI is a bearer-token client. `operations` lists the full registry; `operations --details` shows each operation name and its public, bearer, browser-session, report-capability or conditional access mode, required scope and MCP availability. Registry presence does not guarantee every entry is callable by this client. Browser-session-only operations require the web app; the CLI has no browser-cookie mode.
• Publishing is always an explicit command. Read and draft commands never publish.
• The CLI redacts credentials from console JSON and errors. Use --output only when you need to save a response that includes a newly issued secret; it creates a new file with mode 0600 and refuses to overwrite an existing file.
• Never pass a Supabase service-role key as INDIELOGS_TOKEN.