Catalog PyPI
PACKAGE EXPLORERView in registry

agentic-crew

PyPI

Framework-agnostic AI crew orchestration - declare once, run on CrewAI, LangGraph, or Strands

ai-agentscrewailanggraphmulti-agentorchestrationstrands
Versions collected1
Direct dependencies20From release 0.2.0
Last observed20 Oct, 22:14 UTC

README

Version 0.2.0 documentation

agentic-crew

Framework-agnostic AI crew orchestration - declare once, run on CrewAI, LangGraph, or Strands.

Why agentic-crew?

The AI agent ecosystem is fragmented:

  • CrewAI - Full-featured but heavyweight
  • LangGraph - Great for flows but different API
  • Strands - Lightweight but AWS-specific

agentic-crew solves this with a universal crew format that decomposes to any framework.

Installation

# Core (no framework - auto-detects at runtime)
pip install agentic-crew

# With specific framework
pip install agentic-crew[crewai]      # CrewAI (recommended)
pip install agentic-crew[langgraph]   # LangGraph
pip install agentic-crew[strands]     # AWS Strands

# All frameworks
pip install agentic-crew[ai]

Quick Start

1. Define a Crew (YAML)

# .crewai/manifest.yaml
name: my-package
version: "1.0"

crews:
  analyzer:
    description: Analyze codebases
    agents: crews/analyzer/agents.yaml
    tasks: crews/analyzer/tasks.yaml
# crews/analyzer/agents.yaml
code_reviewer:
  role: Senior Code Reviewer
  goal: Find bugs and improvements
  backstory: Expert at code analysis
# crews/analyzer/tasks.yaml
review_code:
  description: Review the provided code for issues
  expected_output: List of findings with severity
  agent: code_reviewer

2. Run It

from agentic_crew import run_crew

# Auto-detects best framework
result = run_crew("my-package", "analyzer", inputs={"code": "..."})

Or from CLI:

agentic-crew run my-package analyzer --input "Review this code: ..."

Framework Decomposition

The magic happens in core/decomposer.py:

from agentic_crew.core.decomposer import detect_framework, get_runner

# See what's available
framework = detect_framework()  # "crewai", "langgraph", or "strands"

# Get a runner
runner = get_runner()  # Auto-selects best
runner = get_runner("langgraph")  # Force specific

# Build and run
crew = runner.build_crew(config)
result = runner.run(crew, inputs)

Framework Priority

  1. CrewAI (if installed) - Most features, best for complex crews
  2. LangGraph (if CrewAI unavailable) - Good for flow-based logic
  3. Strands (fallback) - Lightweight, minimal deps

Package Integration

Any package can define crews in a .crewai/ directory:

my-package/
├── .crewai/
│   ├── manifest.yaml
│   ├── knowledge/
│   │   └── domain_docs/
│   └── crews/
│       └── my_crew/
│           ├── agents.yaml
│           └── tasks.yaml
└── src/

Then run:

agentic-crew run my-package my_crew --input "..."

Use Cases

1. Connector Builder (vendor-connectors)

A crew that scrapes API docs and generates HTTP connectors:

agentic-crew run vendor-connectors connector_builder \
  --input '{"api_docs": "https://docs.meshy.ai/en"}'

2. Code Generation (any project)

Define crews for your specific domain and run them on any framework.

Development

# Install with dev deps
uv sync --extra dev --extra tests --extra crewai

# Run tests
uv run pytest tests/ -v

# Lint
uvx ruff check src/ tests/ --fix

License

MIT

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 1

Collected releases
VersionPublishedDirect dependenciesOpen version
0.2.08 Dec 202520

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
jbcom/agentic-crew

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 22:14 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:cdd993661e16eea47def5562f7181c5d8dbeb17529faa7ea583bd9891b1ed7c7