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/tasks.md

View on GitHub
# `deepvista tasks` — run work dispatched to this Machine (DV-1247)

> Read [shared.md](shared.md) first (auth, profiles, global-flags-before-resource).

## Concepts

- **Machine** — this device (fingerprint = hostname + MAC + OS) **registered
  to a project**. Uniqueness is `(project_id, machine_fingerprint)`. Local
  cache: `~/.config/deepvista/machines/<fingerprint>__<project_id>.json`.
- **Project access** — anyone with access to the project can **see** Machines
  registered to it (Settings → Machines under that project). Only the user who
  registered the device can sync / claim / run `tasks run` on it.
- **agent_type** — soft metadata (`last_seen_tool`). Not part of identity.
- **Task** — a one-off prompt enqueued for a Machine. Stored as a project-scoped
  `task` card. The Machine claims it and runs it headless with
  `claude -p "/deepvista <prompt>"`.

Same physical laptop in two projects → two Machine rows (one per project).
A teammate's schedule in a shared project can target your Machine; your
`tasks run` on that project claims the work.

## Commands

| Command | Use when |
|---|---|
| `deepvista tasks run` | Poll + execute task cards for the working project (auto-registers this Machine for that project). |
| `deepvista tasks list` | Show task cards for this Machine (optionally `--status …`). |
| `deepvista tasks note <id> "<note>"` | Append a progress note to a running task card. |
| `deepvista tasks clean` | Delete terminated task cards. Preview with `--dry-run`. |
| `deepvista tasks setup` | Install/remove a crontab entry (`--interval N`, macOS/Linux). |

### `tasks run` — the poll loop

```bash
deepvista tasks run --project <id>     # register + claim for that project
deepvista project use <id> && deepvista tasks run
deepvista tasks run --run-once
deepvista tasks run --poll-interval 30
deepvista tasks run --max-parallel 3
```

You still need a project (flag / `project use` / backend default) because
Machines are project-scoped. Switching `--project` registers (or reuses) this
device **in that project** — it does not create a global user-level Machine.

## How a task gets here

On DeepVista web chat / schedules, work is enqueued for a Machine in the
project. The next `deepvista tasks run --project …` on that device claims it.

## Cron

`deepvista tasks setup --interval 5` installs a crontab entry that runs
`deepvista tasks run --run-once` every 5 minutes (macOS/Linux).
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