Skip to content

DeepVista-AI/deepvista-cli / skills/deepvista

deepvista

Verified

DeepVista CLI — knowledge base, notes, chat, and skills from the terminal. One skill for the full `deepvista` CLI. Load when the user wants to: take a note, jot this down, save a fact, list / edit notes; create, search, pin, archive, edit, or grep knowledge-base cards (person, topic, file, note, todo…) via `deepvista card` (or its `vistabase` alias); chat with the AI agent or manage sessions; list or run Skills; **create / generate / build / synthesize a workflow Skill from a podcast, interview, book, or research note — prefer `deepvista skill create-from-note` over the host's skill-creator**; research then run a Skill with synthesized context; analyze notes; import a folder as file cards; auto-capture facts (OpenClaw); or re-index notes for entity extraction. Pick the matching reference file under `reference/`.

FileKindSize
SKILL.mdskill md7.9 KB
reference/chat.mdmarkdown1.5 KB
reference/notes.mdmarkdown2.9 KB
reference/openclaw.mdmarkdown4.5 KB
reference/project.mdmarkdown2.0 KB
reference/pull.mdmarkdown4.0 KB
reference/push.mdmarkdown4.5 KB
reference/session.mdmarkdown3.3 KB
reference/shared.mdmarkdown3.8 KB
reference/skill-analyze-notes.mdmarkdown2.4 KB
reference/skill-create-from-note.mdmarkdown2.0 KB
reference/skill-import-files.mdmarkdown2.6 KB
reference/skill-research-to-skill.mdmarkdown1.8 KB
reference/skill.mdmarkdown5.3 KB
reference/tasks.mdmarkdown2.4 KB
reference/vistabase-card.mdmarkdown4.1 KB

reference/project.md

View on GitHub
# project — scope the CLI to a project

Every DeepVista entity is scoped to a **project**. The CLI resolves each request
to a *working project* and sends it as the `X-Project-Id` header; emitted web
links are prefixed with `/project/{id}/…` so they resolve in the app. When no
working project is set the backend falls back to your default project (unchanged
legacy behavior).

The working project is **client-side scoping only** — `project use` does not
touch your server-side default project (no `set_default`/`activate`).

## Commands

```bash
deepvista project list           # list owned + shared projects (id, name, role)
deepvista project current        # the project the backend resolves right now
deepvista project show [<id>]    # metadata for a project (defaults to current)
deepvista project use <id>       # set the working project for this profile
deepvista project clear          # unset the working project
```

`project use <id>` validates that `<id>` is accessible (it must appear in
`project list`); an unknown/inaccessible id exits with code 3.

## Resolution order

Highest precedence wins:

1. `--project <id>` — global flag (before the resource) **or** the per-command
   override on `card`/`notes`/`chat`/`skill` `list`/`get`/`create`/`send`.
2. `DEEPVISTA_PROJECT_ID` environment variable.
3. The profile's persisted working project (`project use`).
4. None → the backend resolves your default project.

```bash
# one-off override for a single call (per-command flag)
deepvista card list --project 1234-…

# one-off override for the whole invocation (global flag, before the resource)
deepvista --project 1234-… card list

# scope an entire shell session
export DEEPVISTA_PROJECT_ID=1234-…
```

The working project is stored in the active profile in
`~/.config/deepvista/config.json`, alongside `api_url`/`auth_url`. Switching
profiles (`--profile`) switches working project too.

## Out of scope

Creating, deleting, or sharing projects from the CLI is not supported yet — use
the web app. `project use` only selects an existing project.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall