AI/Setup

Connect WorkSpark to your assistant

Two pieces, then you're done: a connection to WorkSpark and a playbook that teaches your assistant to use it properly. On Claude and Cowork, one plugin installs both.

The connection

ws

A small binary that talks to WorkSpark on your behalf. Your assistant's hands.

The playbook

workspark/skills

Instructions for using it correctly — what to ask, what to confirm, what never to invent.

The result

An assistant that logs your work, preps your reviews, and updates OKRs from real records — and asks before it writes.

Jump to your path

Where do you work?

Claude & CoworkOne plugin, no terminal · 2 minGo ↓Codex, OpenCode & othersTwo commands · 3 minGo ↓Managed or custom setupInstall the CLI yourself · 5 minCLI guide →

Claude & Cowork

Both pieces in one plugin
  1. 1

    Download the plugin and upload it

    One file contains both the connection and the playbook. One-click install from the WorkSpark marketplace is coming soon.

    workspark-0.2.2.plugin

    In the desktop app: Customize → Personal plugins → + → Create plugin → Upload plugin → choose the file you just downloaded.

  2. 2

    Allow WorkSpark through the sandbox

    Required in Cowork

    Cowork blocks outbound connections by default. Until you allowlist WorkSpark, every request fails with a network error.

    Settings → Capabilities → Allow network egress. Turn it on, then add both domains under Additional allowed domains:

    app.workspark.ioworkspark.io

    Security note. Claude warns that network egress carries risk — only add domains you trust. app.workspark.io is the WorkSpark API; workspark.io covers sign-in.

  3. 3

    Sign in by asking

    The plugin installs the connection the first time it's used. Then say “Log in to WorkSpark.”

    In Cowork

    The sandbox can't open a browser, so you get a link. Approve it on your own machine, come back and say “done”. Links expire after a few minutes.

    In Claude Code

    The browser opens on your machine and signs you in directly.

  4. 4

    Ask it something

    “Log what I shipped today.”“Prep my self-review for this cycle.”“Which of my OKRs are stale?”“Who on my team has been most active?”

    It confirms before any write, and never invents accomplishments, review content, OKR updates, or survey responses.

Codex, OpenCode & other harnesses

Add both pieces

1 · Install the connection

npm install -g @workspark/cli

Then ws auth login to sign in. Shell script, PowerShell, and manual binaries are in the CLI guide.

2 · Install the playbook

npx skills add workspark/skills

Open source at github.com/workspark/skills.

Restart the harness afterwards. Most agents only load Skills at startup, so a running session won't pick up the new playbook.

If something doesn't work

Every command fails with a network error

Network egress is off, or the two domains aren't allowlisted. Recheck step 2.

It doesn't know about WorkSpark

The playbook isn't loaded. Restart the harness after installing the Skill.

It's writing to the wrong organisation

Ask it to run ws auth whoami, then switch with ws organizations use.

Ready to sharpen your team's execution?

Book an introductory call to see if WorkSpark is the right fit, or explore the product yourself in a free demo environment.

Start free trialBook a demo