Your workspace, from the shell.

Install

Requires the .NET 8 SDK (or newer).

# install globally
dotnet tool install -g ViviScape.CLI

# sign in — browser opens to work.viviscape.io
vs auth login

vs --help

# upgrade later
dotnet tool update -g ViviScape.CLI

If vs isn't found, ensure %USERPROFILE%\.dotnet\tools is on PATH and open a fresh terminal.

How auth works

Browser-based loopback flow — same pattern as gh auth login:

1. vs auth login starts a local listener and opens work.viviscape.io/auth/cli/connect.
2. The bridge page reads your ViviScape Work session and POSTs it back to the CLI.
3. Credentials are stored in Windows Credential Manager (or ~/.viviscape/credentials.json on macOS/Linux, mode 600).

Override the host with VIVISCAPE_BASE_URL (defaults to https://work.viviscape.io).

Sample sessions

# list active companies as JSON, pipe through jq
$ vs companies list --format json | jq '.[].name'

# create a company
$ vs companies add --name "Beacon & Co." --tag enterprise

# open one in your browser
$ vs companies open cmp_4f81

# log 90 minutes against a task
$ vs time add --task tsk_8af2 --minutes 90 --memo "design review"

# my open tasks across all projects
$ vs tasks open --mine

# this week's hours, grouped by project
$ vs insights hours --by project --range thisweek

# add a note to a client
$ vs notes add --client cli_19b7 \
    --title "Discovery call" \
    --body "Needs SSO + SCIM, no AI yet."

# attach a file to that note
$ vs notes attach not_2d10 ./discovery-deck.pdf

# search notes
$ vs notes query "churn risk" --since 30d

Why a CLI?

• Drop into CI pipelines for nightly automation
• Pipe-friendly --format json on every command
• Same identity as the web — every action audit-logged
• Cross-platform: Windows, macOS, Linux