@jive-ai/cli 0.0.31 → 0.0.33

package/README.md

@@ -0,0 +1,109 @@
+# Jive CLI
+
+The official CLI for Jive AI - autonomous development workflows powered by Claude.
+
+## Installation
+
+### npm
+
+```bash
+npm install -g @jive-ai/cli
+```
+
+### Docker
+
+```bash
+docker pull jiveai/task:latest
+```
+
+## Configuration
+
+### Environment Variables
+
+The CLI can be configured using environment variables:
+
+- `JIVE_TASK_IDLE_TIMEOUT` - Minutes of idle time before a task automatically terminates (default: 5). Tasks are ephemeral and will gracefully shutdown after this period of inactivity, freeing up runner capacity. Session data is preserved for resume.
+  - Development: `JIVE_TASK_IDLE_TIMEOUT=10` (10 minutes - more forgiving)
+  - Production: `JIVE_TASK_IDLE_TIMEOUT=5` (5 minutes - default)
+  - CI/CD: `JIVE_TASK_IDLE_TIMEOUT=30` (30 minutes - long builds)
+
+- `JIVE_API_KEY` - Your Jive API authentication key (required for task runners)
+- `JIVE_TEAM_ID` - The team ID to run tasks for (required for task runners)
+- `JIVE_API_URL` - API endpoint (defaults to production)
+- `JIVE_WS_URL` - WebSocket endpoint (defaults to production)
+- `JIVE_LOG_FILE` - MCP server log path (defaults to `/tmp/jive-mcp.log`)
+
+## Docker Image
+
+The docker image is used for each task process container. Whenever you spin up a new task in Jive,
+it will start a new container with this image. You can specify your own custom image in the project settings
+as long as the same entrypoint script is provided. The task runner relies on it.
+
+### Building Your Own Images
+
+You can extend the Jive task runner image to add custom tools or dependencies:
+
+```dockerfile
+FROM jiveai/task:latest
+
+# Add your custom dependencies
+RUN apk add --no-cache python3 py3-pip
+
+# Install additional tools
+RUN pip install --break-system-packages black ruff
+```
+
+## Publishing the Docker Image (Maintainers)
+
+### One-Time Setup
+
+1. Login to Docker Hub:
+   ```bash
+   docker login
+   ```
+
+2. Create a buildx builder for multi-platform builds:
+   ```bash
+   docker buildx create --name mybuilder --use
+   docker buildx inspect --bootstrap
+   ```
+
+### Publishing a New Version
+
+After publishing a new version to npm, publish the corresponding Docker image:
+
+```bash
+cd cli
+npm run docker:publish
+```
+
+This will:
+- Build for both `linux/amd64` and `linux/arm64` platforms
+- Tag with both `latest` and the current package version (e.g., `0.0.31`)
+- Push both tags to Docker Hub
+
+The image pulls the CLI from npm (using the `@jive-ai/cli` package), so make sure you've published to npm first.
+
+### Manual Steps
+
+If you need more control:
+
+```bash
+# Build only (no push)
+npm run docker:build:public
+
+# Push to Docker Hub
+npm run docker:push
+```
+
+## Development
+
+### Local Development with Docker
+
+To test the Docker image with your local code changes:
+
+```bash
+npm run docker:build:local
+```
+
+This builds an image using the local CLI tarball instead of pulling from npm.

package/dist/config-7rVDmj2u.mjs

@@ -0,0 +1,3 @@
+import { A as getProjectConfig, D as clearCredentials, F as saveCredentials, I as saveProjectConfig, L as updateCredentials, M as isProjectInitialized, N as requireAuth, O as getActiveTeamId, P as requireProjectConfig, R as updateProjectConfig, j as getTasksConfigSync, k as getCredentials } from "./index.mjs";
+
+export { getCredentials };

package/dist/graphql-client-DtN1tbTC.mjs

@@ -0,0 +1,3 @@
+import { C as queries, S as mutations, b as cliMutations, x as cliQueries, y as getGraphQLClient } from "./index.mjs";
+
+export { getGraphQLClient };