Skip to content

Add AgenticCodeExecution sample solution - MCP code-execution agents#82

Open
rbogdano wants to merge 6 commits intoopea-project:mainfrom
rbogdano:feature/agentic-code-execution
Open

Add AgenticCodeExecution sample solution - MCP code-execution agents#82
rbogdano wants to merge 6 commits intoopea-project:mainfrom
rbogdano:feature/agentic-code-execution

Conversation

@rbogdano
Copy link
Copy Markdown

@rbogdano rbogdano commented Apr 1, 2026

Adds a new sample solution AgenticCodeExecution — a self-contained MCP-based agentic code execution demo supporting retail, airline, stocks, banking, and triage domains.

What's included:

  • Two-server MCP architecture (tools-server + sandbox-server) with per-session DB isolation
  • Flowise 3.0.12 as visual agent UI (included in docker-compose)
  • Auto-download of tau2-bench databases (airline, retail) on first run
  • LLM deployment guide (Enterprise Inference Helm charts + standalone Docker)
  • 5 domain-specific Flowise agent flow templates and system prompts
  • Comprehensive troubleshooting section (proxy, Flowise SSE, NUMA/NRI, vLLM)

@rbogdano rbogdano force-pushed the feature/agentic-code-execution branch from f82d439 to 794bb42 Compare April 1, 2026 12:56
restart: unless-stopped

# Flowise (visual agent builder UI)
flowise:
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to deploy flowise using docker-compose. It shall be using it from plugins/agenticai

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to follow the convention of the other sample_solutions where the backend and frontend are bundled together in one place — in my case Flowise serves as the frontend. That said, I agree it might be better to just link to plugins/agenticai from here instead of bundling Flowise in docker-compose.

I'll address that in a follow-up commit.

rbogdano added 6 commits April 7, 2026 03:30
MCP-based agentic code execution demo with Flowise, supporting
retail, airline, stocks, banking, and triage domains.

- Two-server MCP architecture: tools-server + sandbox-server
- Flowise 3.0.12 as visual agent UI (docker-compose included)
- Auto-download of tau2-bench databases (airline, retail)
- LLM deployment guide (EI Helm + standalone Docker)
- Comprehensive troubleshooting section
- Per-session database isolation for concurrent users

Source: https://github.com/intel-sandbox/Agentic-Code-Execution
Signed-off-by: Rafal Bogdanowicz <rafal.bogdanowicz@intel.com>
Signed-off-by: Rafal Bogdanowicz <rafal.bogdanowicz@intel.com>
…tead

- Remove Flowise service from docker-compose.yml (use plugins/agenticai)
- Update README to reference EI agenticai plugin for Flowise deployment
- Update Flowise MCP config, troubleshooting sections for K8s context
- Remove FLOWISE_PORT from .env

Signed-off-by: Rafal Bogdanowicz <rafal.bogdanowicz@intel.com>
…to table

Signed-off-by: Rafal Bogdanowicz <rafal.bogdanowicz@intel.com>
Signed-off-by: Rafal Bogdanowicz <rafal.bogdanowicz@intel.com>
Sync with standalone Agentic-Code-Execution repo refactor:
- Replace tools-server/, system-prompts/, data/ with examples/{domain}/ structure
- Each domain (retail, airline, stocks, banking, triage) is self-contained
- Remove start_all.sh (unused)
- Update docker-compose.yml, Dockerfile, .gitignore, README paths
- Update MCP server imports and default DB/session paths

Signed-off-by: Rafal Bogdanowicz <rafal.bogdanowicz@intel.com>
@rbogdano rbogdano force-pushed the feature/agentic-code-execution branch from 5d44018 to 888d65b Compare April 7, 2026 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants