Connects a machine to a session-viz workspace via browser-based OAuth sign-in.
npx skills add https://github.com/QSchlegel/session-viz --skill qsetup-qschlegel
Please help me install this Agent Skill. Skill: qsetup Source: https://github.com/QSchlegel/session-viz/tree/main/plugins/session-viz/skills/qsetup Command: npx skills add https://github.com/QSchlegel/session-viz --skill qsetup-qschlegel
contrib scope (person-blind aggregates, any member) by default or a collab scope (identity-bearing vaults and MCP, admins only) via a flag. - Verified, permissioned storage: Validates the token against the server before writing it to a config.json file with mode 0600 in a 0700 directory, with fallback paths for sandboxed harnesses via SESSION_VIZ_HOME. - Use Case: A developer installs the session-viz plugin on a new laptop and runs the setup command; a browser opens, they approve the consent screen, and the machine is connected without ever handling a credential. ## Quick Start Run the qsetup script with node to open the browser sign-in and connect this machine to your session-viz workspace.High-intent search queries and answers about installing and using this skill.
Run the qsetup script with node, which opens a browser consent screen for sign-in. After you approve, the script exchanges the authorization code for a token and writes it to a local config file automatically.
The setup uses the RFC 8252 native-app flow with PKCE: a code verifier stays in the local process while the browser handles authentication. The token arrives on disk through a loopback callback, so it is never typed, pasted, or shown.
The contrib scope sends person-blind aggregate findings and can be approved by any workspace member. The collab scope covers identity-bearing vaults, task handoff, and MCP access, and requires admin approval. A collab token also works for contrib operations.
Yes. On headless machines, open the printed URL from any browser that can reach the loopback address. For sandboxed harnesses that block writes, set SESSION_VIZ_HOME to a directory inside the workspace before running setup.
The server currently issues authorization codes only to the hardcoded session-viz-cli client id, so dynamically registered clients are rejected with an unknown client_id error. The MCP OAuth path is not live yet and should be left out of setup.
The token is written to a config.json file with mode 0600 inside a 0700 directory, located at SESSION_VIZ_HOME, XDG_CONFIG_HOME/session-viz, or ~/.config/session-viz depending on your environment. Use the --show flag to view the config with the token redacted.
anselsourceCreate and distribute Claude Code plugin marketplaces with marketplace.json.
AltimateAIConfigure Altimate credentials and validate them via datamate_manager.
EveryIncExecutes implementation plans end-to-end with local verification and optional cross-model delegation.
rudrankriyamAutomate App Store Connect app record creation via browser automation.