CrewAI Studio
Build, manage, and run CrewAI crews and tasks through a no-code graphical interface.
- Source repo
- strnad/CrewAI-Studio
- Stars
- ★ 1.4k
- Last updated
- 2mo ago
- License
- MIT
- Primary language
- Python
- FA score
- 51/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformOpenAI API · Claude API
- Cost
- Free software; you pay for model usage
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A non-programmer wants to assemble and test a CrewAI crew through forms instead of writing Python.
- Not a fit if
- Teams wanting active new feature development; repo is low-maintenance
- Users unwilling to manage .env keys and a local crewai.db
- Source review
- 51/100 · Major gaps 2 safety controls not found
What does this agent do, and when should you use it?
CrewAI Studio is a cross-platform Streamlit interface for configuring and running CrewAI crews, agents, and tasks. It targets people who prefer not to write code while providing result history, knowledge sources, CrewAI tools, and custom tools. Crew runs can continue in background threads, be stopped from the application, and leave results available for later review. Supported model backends include OpenAI, Groq, Anthropic, Ollama, Grok, and LM Studio, and a configured crew can be exported as a single-page Streamlit application. It is primarily a self-hosted application, with documented Docker Compose, project-local Conda, and Python virtual-environment installation paths for Windows, Linux, and macOS.
Users define CrewAI crews, agents, and tasks in a Streamlit UI, attach knowledge sources, and select a supported model backend. When started, the application runs the crew in a background-capable thread, lets the user stop it, and records output for later viewing. CrewAI tools can interact with external systems, while documented custom tools cover API calls, file writing, an enhanced code interpreter, and an enhanced web scraper. API keys and other settings are loaded from .env. A finished crew configuration can also be exported as a simple single-page Streamlit app.
- A non-programmer wants to assemble and test a CrewAI crew through forms instead of writing Python.
- An operator needs a long-running crew to continue in the background with a manual stop control.
- A research or content team wants to attach knowledge sources and revisit earlier execution results.
- A developer evaluating model options wants to configure OpenAI, Anthropic, Groq, Grok, Ollama, or LM Studio backends.
- A prototype builder wants to export a configured crew as a small, single-page Streamlit application.
- A team seeking a self-hosted CrewAI GUI wants a choice of Docker Compose, Conda, or venv deployment.
How do you install or deploy this agent?
The virtual-environment route requires Python. On Linux or macOS run:
git clone https://github.com/strnad/CrewAI-Studio.git
cd CrewAI-Studio
./install_venv.sh
./run_venv.shOn Windows run:
git clone https://github.com/strnad/CrewAI-Studio.git
cd CrewAI-Studio
./install_venv.bat
./run_venv.batThe Conda option installs Conda inside the project and does not require an existing Conda installation. On Linux, run ./install_conda.sh followed by ./run_conda.sh; on Windows, use ./install_conda.bat followed by ./run_conda.bat.
For containers, install Docker and Docker Compose, clone and enter the repository, run cp .env_example .env, edit .env with the required API keys and configuration, then run docker-compose up --build. Open http://localhost:8501.
How do you use this agent?
Populate .env with credentials and settings for the chosen providers before starting the application. An OpenAI key may still be required for embeddings used by many tools, even with another model backend; LM Studio users should load an embedding model. Start the appropriate run_venv or run_conda script, or launch docker-compose up --build, then open the Streamlit UI; the documented Docker Compose address is http://localhost:8501. Define the crew, its agents, and its tasks, then add knowledge sources and CrewAI or custom tools as needed. Select a model backend and start the crew; the run can continue in the background or be stopped, and its results can later be reviewed or the crew exported as a single-page Streamlit app.
What are this agent's strengths and limitations?
- Provides a Streamlit GUI for managing CrewAI crews and tasks without requiring hand-written application code.
- Documents Windows, Linux, and macOS support with venv, project-local Conda, and Docker Compose installation choices.
- Supports OpenAI, Groq, Anthropic, Ollama, Grok, and LM Studio backends rather than limiting crews to one model provider.
- Combines result history, knowledge sources, background execution, and stop controls in the same interface.
- Can export a configured crew as a simple single-page Streamlit application.
- The repository is in low-maintenance mode: new features are not actively developed, although security and critical fixes continue and pull requests are welcomed.
- Adopters must manage API keys and other settings in
.env, and cloud providers or real-world tools generally introduce network dependencies. - Many tools may still need an OpenAI key for embeddings even when another model provider is selected.
- LM Studio requires an embedding model to be loaded separately.
- The documented troubleshooting notes warn that new versions can break
crewai.dbcompatibility; that database contains the user's crews.
How does this agent compare with similar options?
Compared with working directly in CrewAI code, CrewAI Studio adds a no-code Streamlit interface, result history, background runs, stop controls, and single-page app export. It also offers three documented deployment approaches—Docker Compose, project-local Conda, and Python venv—and supports several cloud and local model backends.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| CrewAI Studio This agent | 51 · Major gaps | Web appFree + model costs | ★ 1.4k | 2mo ago | Python | OpenAI API · Claude API |
| EDDI Conversational AI Orchestration | 68 · Some gaps | Self-hosted serviceFree + model costs | ★ 386 | 1d ago | Java | OpenAI API |
| iX - Autonomous Agent Platform | 28 · Major gaps | CLIFree + model costs | ★ 1k | 2y ago | Python | OpenAI API |
| OWL Multi-Agent Automation | 39 · Major gaps | CLIFree + model costs | ★ 20k | 7d ago | Python | OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
The README discloses API keys, several external model providers, and real-world tools for API calls, web scraping, file writing, and code interpretation. This gives limited visibility into data flows and external effects, but there is no evidence of least-privilege enforcement, sandboxing, per-action confirmation, destination previews, or tool-scoped authorization, so least_privilege and user_confirmation score 0. Sensitive-data guidance stops at putting keys in .env, without storage, logging, redaction, rotation, or leak-protection controls. Exact dependency pins are a basic safeguard, but the dependency surface is very large and no vulnerability scanning, lock integrity, or update policy is shown. Background jobs can be stopped, results are retained, and database renaming is suggested for troubleshooting, but no general undo or recovery mechanism is documented. The author, upstream tool work, and external tutorial are attributed, although publisher identity remains unknown.
The README, pinned dependencies, and tool-identifier regression tests support a reasonably consistent product account. The tests thoroughly cover stable IDs, translated labels, legacy migration, graceful skipping of unknown tools, and parameter preservation; however, this is evidence for only one narrow subsystem and cannot establish whole-application reliability. Installation paths and versions are explicit across Docker, venv, and Conda, while the exceptionally large dependency set increases availability risk. Unknown tools are handled without crashing, assertions contain diagnostic context, and the README offers troubleshooting steps, but comprehensive UI error messages and systematic exception handling are not evidenced.
The intended audience and scenarios are explicit: non-coders can manage and run CrewAI agents and tasks through a GUI using multiple models, knowledge sources, and tools, justifying full credit for audience_and_scenarios. Some boundaries are disclosed, including possible OpenAI embedding requirements, the need to load an LM Studio embedding model, and low-maintenance status; nevertheless, permissions and limits for file writing, code execution, networking, and individual tools are undefined. Tests show precise resolution of multilingual and legacy tool-selection names, but there is no evidence about agent triggering conditions, ambiguity handling, or task routing. Windows, Linux, macOS, Docker, Conda, and venv are addressed, though platform instructions are uneven and no resource or compatibility matrix is supplied.
The README has clear sections for features, installation, configuration, troubleshooting, tutorials, and maintenance, but lacks deeper reference documentation. Installation receives full credit because it provides concrete commands, prerequisites, environment alternatives, and the local access address. Naming stability receives full credit because tests comprehensively constrain stable internal tool IDs, translated labels, legacy aliases, and database self-healing. Screenshots, a video tutorial, and troubleshooting notes are useful, but there are no complete task examples or substantive FAQ. Low-maintenance status, embedding requirements, and database compatibility problems are disclosed, though limitations are not systematically catalogued. Only MIT metadata is supplied; no license text is included in the evidence. There is no changelog or documented versioning policy, with only issue references and migration tests indicating an update trail. Maintenance responsibility is reasonably clear through the author's security/critical-fix commitment, PR review invitation, and issue support, but no team ownership, response commitment, or formal security contact is shown.
Results history, stoppable background runs, knowledge sources, GUI configuration, and single-page Streamlit export make outputs viewable, reusable, and deployable for ordinary use; concrete output formats, quality controls, and export limitations are not shown. A cross-platform no-code GUI, persistence, and multi-provider support offer clear marginal value over writing CrewAI code directly. Cost-benefit evidence is thin: MIT metadata and local backend options may reduce entry costs, but model/API expense, resource requirements, latency, disk use, and the operational burden of the large dependency set are not documented.
Several important claims are traceable to specific supplied files: requirements.txt records dependency versions, README documents features and installation, and issue-referenced tests specify tool-name compatibility behavior. README, dependencies, and tests provide some corroboration for CrewAI integration, tools, internationalization, and database migration; most feature, platform, and safety claims remain README-only assertions without supporting code or tests. The sources distinguish maintenance status, known caveats, and test expectations and do not claim that tests were executed, but promotional feature statements are not consistently separated from verified facts, preventing full credit.
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- File writing, code interpretation, web scraping, and API calls can create local or external side effects. The supplied evidence shows no sandbox, least-privilege policy, or pre-execution confirmation, so review and restrict tool permissions in an isolated environment.
- Do not assume .env alone protects credentials. Avoid production keys or sensitive knowledge sources until logging, database storage, exports, and third-party provider data handling have been inspected.
- The project is in low-maintenance mode and has a very large dependency set. Perform independent vulnerability scanning, license review, and platform compatibility checks before deployment.
- Database upgrades may break compatibility, and the README suggests renaming crewai.db. Keep a recoverable backup and validate migration before upgrading.
- This assessment uses only the supplied static files; neither the application nor tests were executed, so runtime safety, functional correctness, and cross-platform claims remain unconfirmed.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
v2.0.2 v2.0.2 - Docker build fix
Release notes excerpt
Bugfix release This release fixes the broken Docker build introduced in v2.0.1. If v2.0.1 built fine for you (e.g. an already-resolved environment), there is nothing else in this release. 🐛 Fixed - Docker build failure: ResolutionImpossible on json_repair (#124, fixed in #125). The v2.0.1 dependency sweep (#121) bumped json_repair to 0.60.1, but crewai==1.5.0 hard-pins json-repair==0.25.2, making a clean pip install -r requirements.txt unsolvable. Reverted to 0.25.2 — json_repair had no security advisory, so nothing from the v2.0.1 security fixes is lost. …View on GitHub ↗ -
v2.0.1 v2.0.1 - Security release
Release notes excerpt
Security release This release fixes a critical security vulnerability and clears the outstanding dependency CVEs. All users should upgrade to v2.0.1 immediately. 🔒 Fixed - Critical: Remote Code Execution in the Custom API Tool ([GHSA-hm5m-fhf2-vrpq](https://github.com/strnad/CrewAI-Studio/security/advisories/GHSA-hm5m-fhf2-vrpq), CVSS 9.8). Full details are published in the security advisory. (#120) ⬆️ Dependency security bumps (#121) …View on GitHub ↗ -
v2.0.0 CrewAI Studio v2.0.0
Release notes excerpt
Major maintenance release — tool i18n fixes, a rewritten single-page app export and a large security dependency refresh. Fixed - Tools work again in all languages (#115, #116): tool names are now stable internal identifiers and translations only affect display labels. Agents saved with older (translated or broken) tool names are migrated automatically on load instead of crashing the app. - 10 tools had no translation entry at all (raw tool.* keys were persisted) and the Scrapfly tool referenced a non-existent i18n key — both fixed, with en + zh translations added. …View on GitHub ↗
FAQ
Is OpenAI mandatory?
Can it run entirely on local infrastructure?
What happens if an upgrade breaks existing crews?
crewai.db because new versions can sometimes break compatibility. That file contains the user's crews, so preserving the original file is prudent.