Skip to content

Troubleshooting

Start here:

bash
postlyra status

It reports auth, brand, folders, vault and unmined counts without mining anything.

"No AI backend available"

Neither the claude CLI nor ANTHROPIC_API_KEY was found.

bash
which claude          # should print a path
echo $ANTHROPIC_API_KEY

Install the Claude CLI, or export a key. The tool refuses rather than sending your commit text somewhere you did not choose.

"Not logged in"

Run postlyra login. If it keeps happening, your token was revoked. Check your profile, under API tokens.

"No folders or vault configured"

Run postlyra init and give it at least one folder or a vault path.

"skipping <path> (no git repos found)"

The folder exists but has no .git in it, and no repos one level down. Either point at the repo itself, or at the parent that contains several.

Remember it only looks one level deep. ~/Sites/clients/acme is not found by configuring ~/Sites.

"skipping <base> (no 0-inbox/ directory)"

The vault path needs a 0-inbox/ folder. Create one, point somewhere else, or pass --no-vault.

"nothing new to mine"

Working as intended, in one of two ways:

"nothing new in the window" means no commits or notes at all in the last N days. Widen it: postlyra mine --days 30.

"everything in the window is already mined" means every ref is already attached to an idea. That is dedup doing its job. Widening the window will not help, because those refs are known too. Do some work, then run again.

"This account has N brands"

Pick one:

bash
postlyra brands
postlyra brands use <brand-id>

Or pass --brand <id> for a single run.

"No profile configured for this team yet"

The brand has no content profile, so there is no voice or pillars to ground ideas in. Create one in Studio. See Content profiles.

"Could not find a JSON object in the AI response"

The model returned prose instead of JSON. Usually transient, so try again. If it persists, the model behind your claude CLI may be the problem, and setting ANTHROPIC_API_KEY to use the API path directly is a useful comparison.

The raw response is printed with the error, so you can see what came back.

Ideas are duplicating

They should not. Import is idempotent on sorted source_refs plus headline.

If you see genuine duplicates, the refs differ between runs. Check with:

bash
postlyra mine --dry-run --json

and compare the ref values across two runs. A changing repo label is the usual cause: mining ~/Sites/myproject directly labels it myproject, while mining ~/Sites labels the same repo Sites/myproject. Different labels, different refs.

Pick one shape and stay with it.

Too many mediocre ideas

Lower the count.

bash
postlyra mine --max 3

Asking for 3 tends to give 3 usable ideas. Asking for 12 gives 3 usable ones plus 9 you will dismiss.

A thin persona and voice guide also produce generic output. Filling those in properly is the single biggest quality lever. See Persona.

Commits are missing

Check in order:

  • Are they inside the window? --days N.
  • Are they on another branch? Set allBranches to true.
  • Are they merge commits? Those are excluded deliberately.
  • Is the repo excluded by an exclude pattern?
  • More than 60 commits in that repo? Only the newest 60 are read.

Something else

postlyra mine --dry-run --json shows the full internal state of a run: what was collected, what was filtered, and what the AI would see. Almost every question is answered there.

Postlyra, by MAVA Design