@jive-ai/cli 0.0.26 → 0.0.30

package/package.json

@@ -1,7 +1,7 @@
 {
   "private": false,
   "name": "@jive-ai/cli",
-  "version": "0.0.26",
+  "version": "0.0.30",
   "main": "index.js",
   "files": [
     "dist",
@@ -11,31 +11,45 @@
     "jive": "dist/index.mjs"
   },
   "scripts": {
-    "dev": "npm run build && JIVE_API_URL=http://localhost:5173 npx jive",
+    "dev": "bun run build && JIVE_API_URL=http://localhost:5173 JIVE_WS_URL=ws://localhost:3000 bun run dist/index.mjs",
     "test": "echo \"Error: no test specified\" && exit 1",
     "typecheck": "tsc --noEmit",
-    "build": "tsdown",
+    "build": "tsdown && npm pack && npm install -g jive-ai-cli-*.tgz",
+    "docker:build": "touch jive-ai-cli-0.0.0.tgz && docker build -t jive-task-runner:latest . && rm -f jive-ai-cli-*.tgz",
+    "docker:build:local": "bun run build && docker build --build-arg USE_LOCAL=true -t jive-task-runner:latest .",
     "prepublishOnly": "npm run typecheck && npm run build"
   },
   "author": "",
   "license": "ISC",
   "description": "",
   "devDependencies": {
+    "@types/fs-extra": "^11.0.4",
     "@types/node": "^24.10.1",
     "@types/prompts": "^2.4.9",
+    "@types/ws": "^8.5.13",
     "tsdown": "^0.16.4",
     "tsx": "^4.20.6"
   },
   "dependencies": {
+    "@anthropic-ai/claude-agent-sdk": "^0.1.46",
     "@modelcontextprotocol/sdk": "^1.22.0",
-    "axios": "^1.13.2",
     "chalk": "^5.6.2",
     "change-case": "^5.4.4",
+    "chokidar": "^5.0.0",
+    "cloudflared": "^0.7.1",
     "commander": "^14.0.2",
     "dedent": "^1.7.0",
+    "fs-extra": "^11.3.2",
+    "get-port": "^7.1.0",
+    "graphql": "^16.12.0",
+    "graphql-request": "^7.4.0",
     "gray-matter": "^4.0.3",
+    "js-base64": "^3.7.8",
     "ora": "^9.0.0",
     "prompts": "^2.4.2",
-    "typescript": "^5.9.3"
+    "typescript": "^5.9.3",
+    "uuid": "^13.0.0",
+    "ws": "^8.18.0",
+    "zod": "^3.25.76"
   }
-}
+}

package/dist/config-BP7v03In.mjs

@@ -1,3 +0,0 @@
-import { a as isProjectInitialized, c as saveCredentials, i as getProjectConfig, l as saveProjectConfig, n as getActiveTeamId, o as requireAuth, r as getCredentials, s as requireProjectConfig, t as clearCredentials, u as updateProjectConfig } from "./index.mjs";
-
-export { getCredentials };

package/docs/auth.md

@@ -1,378 +0,0 @@
-# Authentication Commands
-
-Jive CLI requires authentication to access team resources and collaborate with team members. This guide covers all authentication-related commands.
-
-## Overview
-
-Authentication in Jive uses token-based authentication. After logging in or signing up, your credentials are securely stored in `~/.jive/credentials.json` with restricted file permissions (mode 0600).
-
-## Commands
-
-### `jive signup`
-
-Create a new Jive account.
-
-**Usage:**
-```bash
-jive signup
-```
-
-**Interactive Prompts:**
-- **Email:** Your email address for account registration
-- **Password:** Account password (minimum 8 characters)
-- **Confirm Password:** Re-enter password for verification
-
-**Process:**
-1. Prompts for email and password
-2. Validates password requirements (minimum 8 characters)
-3. Calls the Jive API signup endpoint (`/api/auth/signup`)
-4. Automatically saves authentication credentials
-5. Displays success message with suggested next steps
-
-**Output:**
-```
-Account created successfully!
-Credentials saved to /Users/username/.jive/credentials.json
-
-Next steps:
-1. Create a team: jive team create
-2. Initialize Jive in your project: jive init
-```
-
-**Credentials Stored:**
-```json
-{
-  "token": "auth-token-here",
-  "userId": "user-123",
-  "email": "user@example.com"
-}
-```
-
-**Error Conditions:**
-- Email already registered
-- Password too short (< 8 characters)
-- Passwords don't match
-- Network connectivity issues
-
-**Implementation:** `src/commands/auth.ts` (signupCommand)
-
----
-
-### `jive login`
-
-Authenticate with an existing Jive account.
-
-**Usage:**
-```bash
-jive login
-```
-
-**Interactive Prompts:**
-- **Email:** Your registered email address
-- **Password:** Your account password
-
-**Process:**
-1. Prompts for email and password
-2. Calls the Jive API login endpoint (`/api/auth/login`)
-3. Saves authentication credentials to `~/.jive/credentials.json`
-4. Sets file permissions to 0600 (read/write for owner only)
-
-**Output:**
-```
-Login successful!
-Credentials saved to /Users/username/.jive/credentials.json
-```
-
-**Credentials Stored:**
-```json
-{
-  "token": "auth-token-here",
-  "userId": "user-123",
-  "email": "user@example.com"
-}
-```
-
-**Error Conditions:**
-- Invalid email or password
-- Account not found
-- Network connectivity issues
-- API server unavailable
-
-**Security Notes:**
-- Credentials file is created with mode 0600 (only readable by owner)
-- Never share your credentials file
-- The authentication token is used for all API requests
-
-**Implementation:** `src/commands/auth.ts` (loginCommand)
-
----
-
-### `jive logout`
-
-Clear authentication credentials and log out.
-
-**Usage:**
-```bash
-jive logout
-```
-
-**Interactive Prompts:**
-- **Confirmation:** "Are you sure you want to logout?" (Y/n)
-
-**Process:**
-1. Checks if user is currently logged in
-2. Prompts for confirmation
-3. Deletes `~/.jive/credentials.json` file
-4. Displays success message
-
-**Output:**
-```
-Logged out successfully
-```
-
-**Notes:**
-- This only removes local credentials; it doesn't invalidate the token on the server
-- You can log back in at any time with `jive login`
-- Active team configurations in projects remain intact
-
-**Error Conditions:**
-- Not currently logged in (displays "Not logged in" message)
-- User cancels confirmation
-
-**Implementation:** `src/commands/auth.ts` (logoutCommand)
-
----
-
-## Authentication Flow
-
-### First-Time Setup
-
-1. **Sign up for an account:**
-   ```bash
-   jive signup
-   ```
-
-2. **Create or join a team:**
-   ```bash
-   jive team create
-   ```
-   Or accept an email invitation to join an existing team.
-
-3. **Initialize in a project:**
-   ```bash
-   jive init
-   ```
-
-### Returning User
-
-1. **Log in:**
-   ```bash
-   jive login
-   ```
-
-2. **Start using Jive commands:**
-   ```bash
-   jive team list
-   jive subagents pull
-   jive mcp pull
-   ```
-
-## Credentials Storage
-
-### Location
-
-Credentials are stored in:
-```
-~/.jive/credentials.json
-```
-
-**Absolute paths:**
-- macOS/Linux: `/Users/username/.jive/credentials.json`
-- Windows: `C:\Users\username\.jive\credentials.json`
-
-### Format
-
-```json
-{
-  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
-  "userId": "user-abc123",
-  "email": "user@example.com"
-}
-```
-
-### Security
-
-- File permissions set to 0600 (owner read/write only)
-- Token is used in `X-API-Key` header for all API requests
-- Automatically injected by the API client
-
-**Never commit credentials to version control!**
-
-## API Integration
-
-### Authentication Header
-
-All authenticated requests include:
-```http
-X-API-Key: <token-from-credentials>
-```
-
-### Token Handling
-
-The API client (`src/lib/api-client.ts`) automatically:
-- Reads credentials from `~/.jive/credentials.json`
-- Injects the `X-API-Key` header
-- Handles 401 Unauthorized responses by prompting re-authentication
-
-### Session Management
-
-- Tokens do not expire (currently)
-- If you receive authentication errors, try logging out and back in:
-  ```bash
-  jive logout
-  jive login
-  ```
-
-## Troubleshooting
-
-### "Not authenticated" Error
-
-**Symptom:** Commands fail with "Please login first: jive login"
-
-**Solutions:**
-1. Check if credentials file exists:
-   ```bash
-   ls ~/.jive/credentials.json
-   ```
-
-2. Log in again:
-   ```bash
-   jive login
-   ```
-
-3. If signup is needed:
-   ```bash
-   jive signup
-   ```
-
-### "Invalid credentials" Error
-
-**Symptom:** Login fails with incorrect email/password
-
-**Solutions:**
-1. Verify email address is correct
-2. Reset password (if password reset is implemented)
-3. Sign up for a new account if needed:
-   ```bash
-   jive signup
-   ```
-
-### Credentials File Missing
-
-**Symptom:** `~/.jive/credentials.json` doesn't exist
-
-**Solutions:**
-1. Log in to recreate the file:
-   ```bash
-   jive login
-   ```
-
-2. Check file permissions:
-   ```bash
-   ls -la ~/.jive/credentials.json
-   ```
-   Should show `-rw-------` (0600 permissions)
-
-### 401 Unauthorized Errors
-
-**Symptom:** API requests fail with 401 status
-
-**Solutions:**
-1. Log out and log back in:
-   ```bash
-   jive logout
-   jive login
-   ```
-
-2. Verify credentials are valid:
-   ```bash
-   cat ~/.jive/credentials.json
-   ```
-
-3. Check API connectivity:
-   ```bash
-   jive doctor
-   ```
-
-## Environment Variables
-
-### `JIVE_API_URL`
-
-Override the default API URL:
-
-```bash
-export JIVE_API_URL=https://your-custom-api.com
-jive login
-```
-
-**Default:** `https://next.getjive.app`
-
-This affects all API endpoints:
-- `/api/auth/login`
-- `/api/auth/signup`
-- `/api/teams/*`
-- `/api/subagents/*`
-- `/api/mcp-servers/*`
-
-## Security Best Practices
-
-1. **Never share your credentials file**
-   - Don't commit to version control
-   - Don't share via chat or email
-   - Don't copy to shared locations
-
-2. **Use strong passwords**
-   - Minimum 8 characters (enforced)
-   - Mix of letters, numbers, and symbols (recommended)
-   - Unique password for Jive (recommended)
-
-3. **Protect your credentials file**
-   - File permissions are automatically set to 0600
-   - Don't modify permissions to make it world-readable
-   - Keep backups secure
-
-4. **Log out when done**
-   - On shared machines, always log out:
-     ```bash
-     jive logout
-     ```
-
-5. **Monitor access**
-   - Review team member list regularly
-   - Remove users who no longer need access
-
-## Related Commands
-
-- [`jive team create`](./team.md#jive-team-create) - Create a team after signup
-- [`jive team list`](./team.md#jive-team-list) - List teams (requires authentication)
-- [`jive init`](./init.md#jive-init) - Initialize project (requires authentication)
-- [`jive doctor`](./init.md#jive-doctor) - Verify authentication and setup
-
-## Implementation Details
-
-**Source Files:**
-- Main implementation: `src/commands/auth.ts`
-- Configuration helpers: `src/lib/config.ts`
-- API client: `src/lib/api-client.ts`
-
-**Key Functions:**
-- `signupCommand()` - Handles user registration
-- `loginCommand()` - Handles user authentication
-- `logoutCommand()` - Clears credentials
-- `loadCredentials()` - Reads credentials file
-- `saveCredentials()` - Writes credentials file securely
-- `requireAuth()` - Ensures user is authenticated (exits if not)
-
-**API Endpoints:**
-- `POST /api/auth/signup` - Create new account
-- `POST /api/auth/login` - Authenticate existing account

package/docs/getting-started.md

@@ -1,263 +0,0 @@
-# Getting Started with Jive CLI
-
-Jive CLI is a command-line tool for managing MCP (Model Context Protocol) servers, tools, and subagents across teams. It integrates with Claude Code to provide team-based collaboration features for AI development.
-
-## What is Jive?
-
-Jive enables teams to:
-- Share and collaborate on **subagents** (custom AI agents with specialized prompts)
-- Share and manage **MCP servers** (tools that extend Claude's capabilities)
-- Track usage and telemetry across team projects
-- Synchronize AI resources across team members
-
-## Prerequisites
-
-- Node.js installed (for running MCP servers)
-- Claude Code installed
-- A Jive account (created in the app, or via `jive signup`)
-
-## Quick Start
-
-### 1. Install Jive CLI
-
-```bash
-npm install -g @jive-ai/cli
-```
-
-### 2. Create an Account
-
-```bash
-jive signup
-```
-
-You'll be prompted for:
-- Email address
-- Password (minimum 8 characters)
-
-Your credentials are securely stored in `~/.jive/credentials.json`.
-
-### 3. Create or Join a Team
-
-Create a new team:
-```bash
-jive team create
-```
-
-Or accept an invitation to join an existing team (invitations are sent via email).
-
-### 4. Initialize Jive in Your Project
-
-Navigate to your project directory and run:
-
-```bash
-jive init
-```
-
-This command will:
-- Scan and upload any existing MCP servers from `.mcp.json`
-- Scan and upload any existing subagents from `.claude/agents/*.md`
-- Add the `jive-mcp` server to your MCP configuration
-- Install the telemetry plugin for tracking tool usage
-- Create project configuration files in `.jive/`
-
-### 5. Restart Claude Code
-
-After initialization, restart Claude Code to load the new MCP server and telemetry plugin.
-
-## Project Structure
-
-After initialization, Jive creates the following structure:
-
-```
-your-project/
-├── .jive/
-│   ├── config.json          # Project configuration (team ID, API settings)
-│   └── sync.json            # Sync state tracking
-├── .claude/
-│   ├── agents/
-│   │   └── subagent-runner.md  # Dynamic subagent loader
-│   └── plugins/
-│       └── jive-mcp-telemetry/  # Telemetry tracking plugin
-└── .mcp.json                # MCP server configurations (includes jive-mcp)
-```
-
-**Important:** Add these to your `.gitignore`:
-```
-.jive/config.json
-.jive/sync.json
-.claude/plugins/
-```
-
-These are automatically added by `jive init`.
-
-## Core Concepts
-
-### Subagents
-
-Subagents are custom AI agents defined by markdown files with YAML frontmatter. They provide specialized prompts and behaviors for specific tasks.
-
-**Example subagent file** (`.claude/agents/code-reviewer.md`):
-```markdown
----
-name: code-reviewer
-description: Reviews code for best practices and potential issues
-jive-id: "123"
----
-
-You are a code reviewer. Analyze the provided code and:
-1. Identify potential bugs or issues
-2. Suggest improvements for readability
-3. Check for security vulnerabilities
-4. Recommend best practices
-```
-
-### MCP Servers
-
-MCP servers extend Claude's capabilities by providing additional tools. They can:
-- Access external APIs
-- Read and write files
-- Execute commands
-- Interact with databases
-- And much more
-
-Jive helps teams share MCP server configurations across projects.
-
-### Teams
-
-Teams are the organizational unit in Jive. All subagents and MCP servers belong to a team. Team members can:
-- Access shared subagents and MCP servers
-- Collaborate on AI resources
-- View usage analytics and telemetry
-
-## Common Workflows
-
-### Sharing a New Subagent
-
-1. Create a subagent file locally:
-   ```bash
-   jive subagents create
-   ```
-
-2. Push it to your team:
-   ```bash
-   jive subagents push
-   ```
-
-3. Team members can pull it:
-   ```bash
-   jive subagents pull
-   ```
-
-### Sharing a New MCP Server
-
-1. Add the server to your team:
-   ```bash
-   jive mcp add my-server
-   ```
-
-2. Team members can pull it:
-   ```bash
-   jive mcp pull
-   ```
-
-### Keeping Resources in Sync
-
-Pull the latest resources from your team:
-```bash
-jive sync
-```
-
-Check the status of your local resources:
-```bash
-jive status
-```
-
-### Switching Between Teams
-
-If you're a member of multiple teams:
-
-1. List your teams:
-   ```bash
-   jive team list
-   ```
-
-2. Switch to a different team:
-   ```bash
-   jive team switch
-   ```
-
-## Configuration
-
-### API URL
-
-By default, Jive connects to `https://next.getjive.app`. You can override this with the `JIVE_API_URL` environment variable:
-
-```bash
-export JIVE_API_URL=https://your-custom-api.com
-```
-
-### Credentials Location
-
-Credentials are stored in `~/.jive/credentials.json` with secure file permissions (mode 0600).
-
-### Project Configuration
-
-Each project has its own configuration in `.jive/config.json`:
-```json
-{
-  "activeTeamId": "team-123",
-  "apiUrl": "https://next.getjive.app",
-  "telemetry": {
-    "enabled": true
-  },
-  "lastSync": "2025-01-15T10:30:00.000Z"
-}
-```
-
-## Troubleshooting
-
-### Check Installation Health
-
-Run the doctor command to diagnose issues:
-```bash
-jive doctor
-```
-
-This checks:
-- Authentication status
-- Project initialization
-- MCP server configuration
-- Subagent runner installation
-- Telemetry plugin setup
-- API connectivity
-- Team membership
-
-### Common Issues
-
-**"Not authenticated"**
-- Run `jive login` to authenticate
-
-**"Project not initialized"**
-- Run `jive init` in your project directory
-
-**"Cannot find team"**
-- Ensure you've created or joined a team with `jive team create` or accepted an invitation
-
-**MCP server not loading**
-- Restart Claude Code after running `jive init`
-- Check `.mcp.json` for the `jive-mcp` entry
-- Run `jive doctor` to verify configuration
-
-## Next Steps
-
-- Learn about [Authentication Commands](./auth.md)
-- Set up your [Team](./team.md)
-- Explore [Subagent Management](./subagents.md)
-- Configure [MCP Servers](./mcp.md)
-- Master [Synchronization](./sync.md)
-
-## Getting Help
-
-- Run `jive --help` to see all available commands
-- Run `jive <command> --help` for command-specific help
-- Report issues at: https://github.com/anthropics/jive-cli/issues