Vibe AIGC
A New Paradigm for Content Generation via Agentic Orchestration
Based on arXiv:2602.04575
📚 Documentation | 🚀 Quick Start | 📖 API Reference
What is Vibe AIGC?
Vibe AIGC bridges the Intent-Execution Gap in AI content generation. Instead of prompt engineering, you provide a Vibe — a high-level representation of your creative intent — and the system automatically decomposes it into executable workflows.
from vibe_aigc import MetaPlanner, Vibe
# Express your intent
vibe = Vibe(
description="Create a cinematic sci-fi trailer",
style="dark, atmospheric, Blade Runner aesthetic",
constraints=["under 60 seconds", "no dialogue"]
)
# Let the Meta-Planner handle the rest
planner = MetaPlanner()
result = await planner.execute(vibe)
Architecture (Paper Section 5)
The implementation follows the paper's three-part architecture:
| Component | Purpose | Module |
|---|---|---|
| MetaPlanner | Decomposes Vibes into workflows | vibe_aigc.planner |
| KnowledgeBase | Domain expertise for intent understanding | vibe_aigc.knowledge |
| ToolRegistry | Atomic tools for content generation | vibe_aigc.tools |
from vibe_aigc import MetaPlanner, Vibe, create_knowledge_base, create_default_registry
# The full architecture
kb = create_knowledge_base() # Film, writing, design, music knowledge
tools = create_default_registry() # LLM, templates, combine tools
planner = MetaPlanner(knowledge_base=kb, tool_registry=tools)
# Query knowledge for "Hitchcockian suspense" → technical specs
result = kb.query("Hitchcockian suspense")
# Returns: camera techniques, lighting specs, editing patterns
Features
- 🎯 Vibe-based Planning — High-level intent → executable workflows
- 🧠 Domain Knowledge — Built-in expertise for film, writing, design, music
- 🔧 Tool Library — Pluggable tools for actual content generation
- ⚡ Parallel Execution — Independent nodes run concurrently
- 🔄 Adaptive Replanning — Automatic recovery from failures
- 💾 Checkpoint/Resume — Save and restore workflow state
- 📊 Progress Tracking — Real-time callbacks and visualization
- 🎨 Workflow Visualization — ASCII and Mermaid diagrams
LLM Providers
Vibe AIGC supports multiple LLM backends with auto-detection:
| Provider | API Key | Model Example |
|---|---|---|
| OpenAI | OPENAI_API_KEY |
gpt-4 |
| Anthropic | ANTHROPIC_API_KEY |
claude-sonnet-4-20250514 |
| Ollama | None (local) | qwen2.5:14b |
from vibe_aigc import MetaPlanner, LLMConfig
# Auto-detect (checks env vars, falls back to Ollama)
planner = MetaPlanner()
# Explicit Ollama (no API key needed!)
config = LLMConfig.for_ollama(
host="http://localhost:11434", # or your GPU server
model="qwen2.5:14b"
)
planner = MetaPlanner(llm_config=config)
# Explicit OpenAI
config = LLMConfig.for_openai(model="gpt-4o")
planner = MetaPlanner(llm_config=config)
Installation
pip install vibe-aigc
CLI Usage
# Generate a workflow plan
vibe-aigc plan "Create a blog post about AI" --style "informative" --format ascii
# Execute a vibe
vibe-aigc execute "Design a landing page" --visualize --checkpoint
# Manage checkpoints
vibe-aigc checkpoints --list
Quick Example
import asyncio
from vibe_aigc import Vibe, MetaPlanner
async def main():
vibe = Vibe(
description="Write a blog post about AI agents",
style="informative, engaging",
constraints=["under 1000 words"]
)
planner = MetaPlanner()
result = await planner.execute_with_visualization(vibe)
print(f"Status: {result.get_summary()['status']}")
asyncio.run(main())
Architecture
User Vibe → MetaPlanner → Agentic Pipeline → Execution → Result
↑ ↓
└──── Feedback Loop ────────┘
Documentation
Contributing
Contributions welcome! See CONTRIBUTING.md for guidelines.
License
MIT — see LICENSE for details.
Citation
@article{vibe-aigc-2025,
title={Vibe AIGC: A New Paradigm for Content Generation via Agentic Orchestration},
journal={arXiv preprint arXiv:2602.04575},
year={2025}
}
Metadata
Release files for vibe-aigc 0.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vibe_aigc-0.7.1.tar.gz | 207.2 kB | Without provenance | Details for vibe_aigc-0.7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vibe_aigc-0.7.1-py3-none-any.whl | Python 3 | none | any | Details for vibe_aigc-0.7.1-py3-none-any.whl |
Total release size: 396.4 kB
Release files / vibe_aigc-0.7.1.tar.gz
| Download URL | vibe_aigc-0.7.1.tar.gz |
|---|---|
| Size | 207.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3656ca8063a5519c3b50c0730afb927314ab9220ced4b8addf757cbc1cdb5635
|
|
BLAKE2b-256 checksum How to use checksums |
ca579a94325e3c82c41cc5172d1920163da74816ab3df596c3bda00e5e617c3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / vibe_aigc-0.7.1-py3-none-any.whl
| Download URL | vibe_aigc-0.7.1-py3-none-any.whl |
|---|---|
| Size | 189.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
730581d96949459e592ab1586c68e54dae8bb10156279adb590fb4f26c1cdfc5
|
|
BLAKE2b-256 checksum How to use checksums |
ff85d49acfaf0806827d0c29f6c1611a4a22750f98311cc9d5b063e82e779217
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for vibe-aigc 0.7.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.