PRODUCT GUIDE / PRODUKTLEITFADEN
Vigthoria CLI
Vigthoria CLI is the terminal entry point for authenticated Vigthoria development. Use it to retrieve a Community repository and continue a portable Prompt Engine plan in a local project. CLI 2.1.2 preserves the approved plan files and binary project assets instead of dropping the hidden plan folder.
Your first workflow
- 01
Install the current signed CLI and sign in.
- 02
Save an approved plan in your chosen Community repository.
- 03
Use the displayed repo pull command with a new local output folder.
- 04
Open the folder, synchronize the plan and inspect the next package.
vigthoria --version vigthoria --help # Use the repository and plan IDs displayed in Prompt Engine: vigthoria repo pull YOUR_REPOSITORY_ID --output ./new-local-project cd new-local-project node .vigthoria/plans/YOUR_PLAN_ID/workloop.cjs sync node .vigthoria/plans/YOUR_PLAN_ID/workloop.cjs status node .vigthoria/plans/YOUR_PLAN_ID/workloop.cjs next
Replace both IDs with your own project values. Sign in through the official client first. Keep account credentials outside source control.
Available working areas
Terminal agent and chat
Use agent or chat for a bounded development conversation. Selected workspace source is sent to the private cloud project mirror; returned file changes require approval by default.
Authenticated repository handoff
Retrieve a repository into a new local folder without silently overwriting existing files. Follow the command shown for your own project.
Keep the approved plan
The master plan, rules, numbered packages and runner travel together under .vigthoria/plans/. Local credentials and runtime receipts are excluded.
Synchronize and inspect progress
The plan runner provides sync, status and next. A workloop loads a bounded package so the next task keeps the shared project direction.
Choose the complete download path
For repositories too large for the inline API, the CLI stops before partial writes and directs you to the full authenticated ZIP.
Optional Continuity memory
With the matching connection, checkpoint, recall and compact preserve structured project context across sessions.
Check the actual result
A local repository copy with portable planning files and exact binary assets.
Review the output against your task before sharing, publishing or relying on it. Retain the project files or records needed to continue.
Access and product scope
Install from the official DevTools center and follow its Node.js and operating-system requirements. Use standalone CLI 2.1.2 or later for this plan handoff.
A terminal agent still needs an authorized account and task-specific checks. Installation alone does not grant access to another user’s projects.
If the next step does not work
I reach sign-in or access is denied.
Sign in with the intended Vigthoria account and reopen this product. Check the selected project, owner or team role and the current product entitlement in User Hub.
The task is queued or a required feature is unavailable.
Inspect the actual job and service state. Check whether the chosen route needs a provider connection, device support, signing setup or an enabled account feature. Keep a saved copy before retrying a completed action.
I need product support.
Include the product, action, time, visible error and relevant job or project identifier. Use a minimal example and keep passwords, secret keys and confidential source material out of the public form.