> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sovara-labs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Project Issues

> Read, create, comment on, and close Sovara project issues from the CLI.

Use project issues to track concrete follow-up work discovered while inspecting
or improving an agent. Every command requires `--project-id`. A selector may
be a full project ID, an unambiguous ID prefix, or an exact project name.

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
PROJECT="support-agent"

sovara issues list --project-id "$PROJECT" --status open
sovara issues get 42 --project-id "$PROJECT"
sovara issues create --project-id "$PROJECT" \
  --title "Retry behavior is unclear" \
  --body "The timeout path should follow lesson #17."
sovara issues comment 42 --project-id "$PROJECT" \
  --body "Reproduced in the latest run."
sovara issues close 42 --project-id "$PROJECT"
```

Issue reference arguments are positive numbers without a leading `#`. `list`
defaults to open issues and supports `--status open|closed`,
`--view all|assigned|created`, `--query`, `--limit`, and `--offset`.

Issues and lessons share a project reference namespace so Markdown bodies and
comments can mention a lesson with `#N`. The `issues get` and `issues comment`
commands reject references that resolve to lesson comments.

Commands print JSON for reliable use by coding assistants. Creating,
commenting, and closing are user-attributed mutations and should only be run
when the user clearly requests the change.