The official CLI for Jive AI - autonomous development workflows powered by Claude.
The official CLI for Jive AI - autonomous development workflows powered by Claude.
``bash`
npm install -g @jive-ai/cli
`bash`
docker pull jiveai/task:latest
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.JIVE_TASK_IDLE_TIMEOUT=10
- Development: (10 minutes - more forgiving)JIVE_TASK_IDLE_TIMEOUT=5
- Production: (5 minutes - default)JIVE_TASK_IDLE_TIMEOUT=30
- CI/CD: (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)
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.
You can extend the Jive task runner image to add custom tools or dependencies:
`dockerfile
FROM jiveai/task:latest
Note: The base image is Debian-based (bookworm-slim), so use
apt-get for package management.Publishing the Docker Image (Maintainers)
$3
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
`$3
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 HubThe image pulls the CLI from npm (using the
@jive-ai/cli package), so make sure you've published to npm first.$3
If you need more control:
`bash
Build only (no push)
npm run docker:build:publicPush to Docker Hub
npm run docker:push
`Development
$3
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.