Crowe Nimbus
Universal AI agent powered by the CroweLM model stack on Azure AI Foundry. The default lineup now fronts gpt-5.4 as CroweLM Titan, gpt-5.4-pro as CroweLM Apex, and claude-opus-4-6 as CroweLM Prime, alongside CroweLM Sovereign, Nexus, Nano, Dense, and the specialist Azure tiers.
Install
pip install crowe-nimbus
npm i @michaelcrowe11/crowe-nimbus
Setup
- Deploy the CroweLM-backed Foundry models on Azure AI Foundry
- Configure credentials:
cp .env.example .env
# Fill in the Azure endpoints and API keys for the CroweLM resources
- Authenticate with Azure:
az login
- Verify the model stack:
crowe-nimbus deploy
- Start chatting:
crowe-nimbus
Usage
crowe-nimbus # Interactive chat (default)
crowe-nimbus chat # Interactive chat session
crowe-nimbus run "prompt" # Single prompt, get response
crowe-nimbus deploy # Verify provider health across the CroweLM stack
crowe-nimbus models sync --account <account> --resource-group <resource-group>
crowe-nimbus status # Show agent status
crowe-nimbus tools # List available tools
CroweLM Apex is wired to stream reasoning summaries through both the terminal UI and crowe-nimbus headless when the Azure Responses API emits them, so hosts that consume the JSON event stream can render reasoning deltas before answer tokens.
Extra Models
The base MODEL_CHAIN can now be extended without editing source. Crowe Logic will load extra model entries from:
CROWE_LOGIC_EXTRA_MODELS_JSONCROWE_LOGIC_EXTRA_MODELS_PATHconfig/models.extra.json~/.config/crowe-logic/models.extra.json~/.crowe-logic/models.extra.json
Start from config/models.extra.example.json and save your generated file as config/models.extra.json, or point CROWE_LOGIC_EXTRA_MODELS_PATH at it.
If you already have Azure deployments and want to turn them into Foundry model entries, generate the file with:
crowe-nimbus models sync --account <account> --resource-group <resource-group>
By default that writes to ~/.config/crowe-logic/models.extra.json, which the runtime already loads. Use --output config/models.extra.json if you want a project-local registry instead.
You can also sync from a saved Azure CLI payload:
az cognitiveservices account deployment list --name <account> --resource-group <resource-group> --output json > deployments.json
crowe-nimbus models sync --input deployments.json --output config/models.extra.json
Tools (79)
| Category | Tools | Description |
|---|---|---|
| Filesystem | 4 | Read, write, edit, list files and directories |
| Shell | 1 | Execute commands with timeout and working directory |
| Web & Search | 3 | Web search, grep/ripgrep, URL fetching |
| Git | 5 | Status, diff, log, commit, clone |
| Browser Automation | 5 | Playwright-based navigation, screenshots, interaction |
| macOS / AppleScript | 3 | System automation, app control, notifications |
| iTerm2 | 18 | Windows, tabs, panes, broadcast, badges, colors, variables |
| Quantum Computing | 4 | QubitFlow circuits, Synapse evaluation, Trinity pipeline |
| Music Composition | 11 | Talon engine -- chords, drums, melody, emotion, quantum composition |
| Vision & Image | 2 | Multi-backend photo analysis (OpenRouter, Crowe Vision) |
| Video Generation | 1 | CroweLM Motion text/image-to-video on Azure AI Foundry |
| CroweLM Training | 10 | Dataset management, curation, fine-tuning pipeline |
| CroweLM Pipeline | 4 | Staging, promotion, agent runner, audit logs |
| Crowe Logic Platform | 4 | Chat, vision, grow logs, SOP generation |
| MCP Client | 4 | Search registry, list tools, call tools, stop servers |
MCP Server
The Crowe Logic platform is also available as a standalone MCP server for any MCP client:
uvx crowe-logic-mcp
See crowe-logic-mcp for configuration details.
Specialized Agents
| Agent | Focus |
|---|---|
cultivation |
Mushroom cultivation with Crowe Logic platform integration |
quantum |
Quantum computing with QubitFlow + Synapse + Trinity bridge |
music |
Music composition with Talon engine |
code |
General software development |
research |
Web research and analysis |
Environment Variables
| Variable | Description |
|---|---|
PROJECT_ENDPOINT |
Legacy Azure AI Foundry project endpoint |
MODEL_DEPLOYMENT_NAME |
Legacy Azure Agents deployment name |
AZURE_CORE_ENDPOINT |
Core CroweLM Azure OpenAI endpoint (gpt-5.4-pro, gpt-5.4-nano, Kimi-K2.5) |
AZURE_CORE_API_KEY |
API key for the core CroweLM Azure OpenAI endpoint |
AZURE_8909_ENDPOINT |
Dedicated Azure OpenAI endpoint for CroweLM Titan (gpt-5.4) |
AZURE_8909_API_KEY |
API key for the CroweLM Titan endpoint |
AZURE_4291_ENDPOINT |
Dedicated Azure OpenAI endpoint for CroweLM Oracle (grok-4-20-reasoning) |
AZURE_4291_API_KEY |
API key for the CroweLM Oracle endpoint |
AZURE_7858_ENDPOINT |
Azure OpenAI endpoint for CroweLM Reason, Vector, and Forge |
AZURE_7858_API_KEY |
API key for the CroweLM Reason / Vector / Forge endpoint |
AZURE_9536_ENDPOINT |
Azure OpenAI endpoint for CroweLM Edge and Atlas |
AZURE_9536_API_KEY |
API key for the CroweLM Edge / Atlas endpoint |
AZURE_ANTHROPIC_ENDPOINT |
Azure Anthropic endpoint for CroweLM Prime (claude-opus-4-6) |
AZURE_ANTHROPIC_API_KEY |
API key for the CroweLM Prime endpoint |
AZURE_1960_ANTHROPIC_ENDPOINT |
Azure Anthropic endpoint for CroweLM Sovereign and Classic |
AZURE_1960_API_KEY |
API key for the CroweLM Sovereign / Classic endpoint |
AZURE_GLM_ENDPOINT |
Optional GLM endpoint for CroweLM Dense (FW-GLM-5) |
AZURE_GLM_API_KEY |
API key for the CroweLM Dense endpoint |
AZURE_SORA_ENDPOINT |
Optional dedicated CroweLM Motion endpoint; falls back to AZURE_CORE_ENDPOINT |
AZURE_SORA_API_KEY |
Optional dedicated CroweLM Motion API key; falls back to AZURE_CORE_API_KEY |
AZURE_SORA_DEPLOYMENT_NAME |
CroweLM Motion deployment name, usually sora-2 |
OPENROUTER_API_KEY |
OpenRouter API key (vision fallback) |
CROWE_LOGIC_DEPLOY_TIMEOUT_SECONDS |
Optional timeout for crowe-nimbus deploy provider checks; defaults to 8 |
CROWE_LOGIC_URL |
Crowe Logic platform URL |
CROWE_LOGIC_KEY |
Crowe Logic API key |
Docker
docker pull michaelcrowe1111/crowe-logic:latest
docker run -it --env-file .env michaelcrowe1111/crowe-logic
GPU variant for fine-tuning:
docker build --target gpu -t crowe-logic:gpu .
Requirements
- Python 3.10+
- Azure AI Foundry account with the CroweLM lineup deployed (
gpt-5.4,gpt-5.4-pro,claude-opus-4-6, plus any optional specialist tiers you want enabled) - Azure CLI (
az login) for authentication
Author
Michael Crowe -- Crowe Logic, Inc.
License
MIT
Metadata
Release files for crowe-nimbus 0.5.0
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 |
|---|---|---|---|---|
| crowe_nimbus-0.5.0.tar.gz | 1.0 MB | Without provenance | Details for crowe_nimbus-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| crowe_nimbus-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for crowe_nimbus-0.5.0-py3-none-any.whl |
Total release size: 2.1 MB
Release files / crowe_nimbus-0.5.0.tar.gz
| Download URL | crowe_nimbus-0.5.0.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a61d83c284d5e83ccbd8a8de832cf05dded0cad1f849d22592c30e2c7c1c474
|
|
BLAKE2b-256 checksum How to use checksums |
c8ac8c323d064f44bd16e85e737b61428aa7329726b7b65c3c8042b7521e6e83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / crowe_nimbus-0.5.0-py3-none-any.whl
| Download URL | crowe_nimbus-0.5.0-py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11f139afd884f7699d2dffd2fb039f7c9795b96063b191f66f0d41095ea16150
|
|
BLAKE2b-256 checksum How to use checksums |
ed8d6968eeb13d900f3c88f0b784ce6c1d8d5642bd4f0403ef50fcfb5c68087b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for crowe-nimbus 0.5.0
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.