# PraisonAI - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `MervinPraison/PraisonAI` - capability: PraisonAI 🦞 — Hire a 24/7 AI Workforce. Stop writing boilerplate and start shipping autonomous self-improving agents that research, plan, code, and execute tasks. Deployed in 5 lines of code with built-in memory, RAG, and support for 100+ LLMs. - expected_user_outcome: PraisonAI 🦞 — Hire a 24/7 AI Workforce. Stop writing boilerplate and start shipping autonomous self-improving agents that research, plan, code, and execute tasks. Deployed in 5 lines of code with built-in memory, RAG, and support for 100+ LLMs. ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **PraisonAI Overview and System Architecture**: importance `high` - source_paths: README.md, AGENTS.md, src/praisonai-agents/README.md, src/praisonai-agents/praisonaiagents/__init__.py, src/praisonai-agents/pyproject.toml - **Core SDK: Agent, Agents, Memory, and Workflows**: importance `high` - source_paths: src/praisonai-agents/praisonaiagents/agent/agent.py, src/praisonai-agents/praisonaiagents/agents/agents.py, src/praisonai-agents/praisonaiagents/agent/autonomy.py, src/praisonai-agents/praisonaiagents/agent/memory_mixin.py, src/praisonai-agents/praisonaiagents/agent/handoff.py - **Tools, MCP Protocol, and LLM Provider Integration**: importance `high` - source_paths: src/praisonai-agents/praisonaiagents/tools/tools.py, src/praisonai-agents/praisonaiagents/tools/decorator.py, src/praisonai-agents/praisonaiagents/tools/registry.py, src/praisonai-agents/praisonaiagents/mcp/mcp.py, src/praisonai-agents/praisonaiagents/mcp/mcp_transport.py - **CLI, UI Surfaces, Workflows, and Deployment**: importance `high` - source_paths: src/praisonai/praisonai/cli/main.py, src/praisonai/praisonai/cli/commands/agents.py, src/praisonai/praisonai/cli/commands/workflow.py, src/praisonai/praisonai/cli/commands/claw.py, src/praisonai/praisonai/cli/commands/flow.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `8b80fa59cf276d8776398bb1501da62cb649a7bc` - inspected_files: `README.md`, `examples/README.md`, `examples/acp/README.md`, `examples/acp/basic_acp_server.py`, `examples/acp/custom_agent_acp.py`, `examples/ag2/ag2_basic.yaml`, `examples/ag2/ag2_bedrock.yaml`, `examples/ag2/ag2_multi_agent.yaml`, `examples/agent_centric_api.py`, `examples/agent_tools/agent_centric_example.py`, `examples/approval/README.md`, `examples/approval/agent_approval.py`, `examples/approval/discord_approval.py`, `examples/approval/http_approval.py`, `examples/approval/slack_approval.py`, `examples/approval/telegram_approval.py`, `examples/async_runs/README.py`, `examples/async_runs/sdk_submit_poll_result.py`, `examples/background/basic_background.py`, `examples/basic/calculator_with_tests.py` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/MervinPraison/PraisonAI/issues/1590 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/MervinPraison/PraisonAI/issues/1941 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/MervinPraison/PraisonAI/issues/1936 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/MervinPraison/PraisonAI/issues/2125 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/MervinPraison/PraisonAI/issues/1654 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/MervinPraison/PraisonAI - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/MervinPraison/PraisonAI - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: downstream_validation.risk_items | https://github.com/MervinPraison/PraisonAI - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: risks.scoring_risks | https://github.com/MervinPraison/PraisonAI - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/MervinPraison/PraisonAI/issues/2153 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.