Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Imbi Automations CLI

Tests Docker Build PyPI Version Docker Hub GHCR

CLI tool for executing automated workflows across Imbi projects with AI-powered transformations and GitHub PR integration.

Overview

Imbi Automations is a comprehensive CLI framework that enables bulk automation across software project repositories with deep integration to the Imbi project management system. The tool supports multiple workflow types with advanced filtering, conditional execution, and AI-powered transformations.

Key Features

  • GitHub Integration: GitHub API integration with comprehensive repository operations
  • Workflow Engine: Action-based processing with conditional execution
  • AI Integration: Claude Code SDK for intelligent transformations
  • Batch Processing: Concurrent processing with resumption capabilities
  • Template System: Jinja2-based file generation with full project context
  • Advanced Filtering: Target specific project subsets with multiple criteria

Action Types

  • Callable Actions: Direct method calls on client instances
  • Claude Code: Comprehensive AI-powered code transformations
  • Docker Operations: Container-based file extraction and manipulation
  • Git Operations: Version control operations and branch management
  • File Actions: Copy, move, delete, and regex replacement operations
  • Shell Commands: Execute arbitrary commands with template variables
  • Template System: Generate files from Jinja2 templates

Documentation

Documentation is available at https://aweber-imbi.github.io/imbi-automations/.

Quick Start

# Run workflows
# Note: Each workflow directory should contain workflow.toml (or config.toml for backward compatibility)
imbi-automations config.toml workflows/workflow-name --all-projects

# Resume from a specific project
imbi-automations config.toml workflows/workflow-name --all-projects --start-from-project my-project-slug

# Run using Docker:

```bash
docker run --rm \
  -v $(pwd)/config.toml:/config/config.toml:ro \
  -v $(pwd)/workflows:/workflows:ro \
  -v ~/.ssh:/root/.ssh:ro \
  -v imbi-cache:/cache \
  aweber/imbi-automations:latest /config/config.toml /workflows/my-workflow --all-projects

Installation

Using uv

uv tool install imbi-automations
uv tool run imbi-automations config.toml workflows/my-workflow --all-projects

From PyPI

pip install imbi-automations
imbi-automations config.toml workflows/my-workflow --all-projects

Docker Installation

Pre-built multi-architecture images are automatically published to both Docker Hub and GitHub Container Registry on every release:

# Pull from Docker Hub (recommended)
docker pull aweber/imbi-automations:latest

# Or pull from GitHub Container Registry
docker pull ghcr.io/aweber-imbi/imbi-automations:latest

# Or use a specific version
docker pull aweber/imbi-automations:1.0.0
docker pull ghcr.io/aweber-imbi/imbi-automations:1.0.0

# Run with docker-compose (recommended)
docker-compose run --rm aweber/imbi-automations /config/config.toml /workflows/my-workflow --all-projects

# Or run directly with docker (Docker Hub)
docker run --rm \
  -v $(pwd)/config.toml:/config/config.toml:ro \
  -v $(pwd)/workflows:/workflows:ro \
  -v ~/.ssh:/root/.ssh:ro \
  -v imbi-cache:/cache \
  aweber/imbi-automations:latest /config/config.toml /workflows/my-workflow --all-projects

# Or run with GHCR
docker run --rm \
  -v $(pwd)/config.toml:/config/config.toml:ro \
  -v $(pwd)/workflows:/workflows:ro \
  -v ~/.ssh:/root/.ssh:ro \
  -v imbi-cache:/cache \
  ghcr.io/aweber-imbi/imbi-automations:latest /config/config.toml /workflows/my-workflow --all-projects

Build from source:

docker build -t imbi-automations:latest .

Docker Volume Mounts:

  • /config/config.toml - Configuration file (read-only recommended)
  • /workflows - Workflows directory (read-only recommended)
  • /cache - Metadata cache directory (persistent)
  • /workspace - Temporary working directory for repo clones
  • /root/.ssh - SSH keys for git operations (read-only)
  • /root/.gnupg - GPG keys for commit signing (optional, read-only)

Important Notes:

  • Claude Code in containers may have limitations with interactive features
  • Ensure SSH keys have proper permissions (0600) when mounting
  • API keys should be in config.toml for security
  • Use named volumes for cache to improve performance across runs

Development Setup

git clone https://github.com/AWeber-Imbi/imbi-automations.git
cd imbi-automations
uv sync --all-groups --all-extras --frozen
uv run pre-commit install --install-hooks

Release files for imbi-automations 2.0.0b2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for imbi-automations 2.0.0b2
File Size Uploaded
imbi_automations-2.0.0b2.tar.gz 373.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for imbi-automations 2.0.0b2
File Interpreter ABI Platform
imbi_automations-2.0.0b2-py3-none-any.whl Python 3 none any Details

Total release size: 510.6 kB

Release files / imbi_automations-2.0.0b2.tar.gz

Download URL imbi_automations-2.0.0b2.tar.gz
Size 373.1 kB
Tags Source
SHA-256 checksum
How to use checksums
a07ea6173bfd416eeee47ddd33985af218e8704d8c96295c64a957a13b33e554
BLAKE2b-256 checksum
How to use checksums
b47eed62869ba7d37909344e81566c7a5af7091c46801d2deec84df84cbb25ec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.

Transparency log

Release files / imbi_automations-2.0.0b2-py3-none-any.whl

Download URL imbi_automations-2.0.0b2-py3-none-any.whl
Size 137.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6048c2b22423c5a8b0cdf9e835dd0c8ecee40bcc536e205c22b2dde9a4d32044
BLAKE2b-256 checksum
How to use checksums
ffd05da91fb7dd9f1c138101aa62cbfc33a819e1877ab2932d1fb88efdd558bf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.

Transparency log

Release history Release notifications | RSS feed

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page