[Feature] Integrate TerminalToolkit with BaseRuntime module

[CamelAIorg]

Problem

TerminalToolkit implements its own Docker backend via use_docker_backend, but camel/runtimes/ already provides runtime abstractions: DockerRuntime, DaytonaRuntime, RemoteHttpRuntime, etc.

Proposal

Add runtime: Optional[BaseRuntime] parameter:

# Docker
toolkit = TerminalToolkit(runtime=DockerRuntime(image="python:3.10"))

# Daytona
toolkit = TerminalToolkit(runtime=DaytonaRuntime(...))

# Local (default)
toolkit = TerminalToolkit()

Benefits

• Unified architecture, reuse existing runtime code
• Support more execution environments
• Remove ~100 lines of duplicated Docker code

Files

• camel/toolkits/terminal_toolkit/terminal_toolkit.py
• camel/runtimes/base.py

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• [Feature Request] Integrate Terminal Toolkit #1765

Related Issues

• [Feature Request] CodeAct Agent for OWL #1823
• [Feature Request] Enhancing terminal toolkit and docker runtime to support more terminal tasks #2913
• [Feature Request] TerminalToolkitDocker, agent interacting with docker environment with tmux session #3008
• [Feature Request] Support custom backends for Toolkits #3502
• [Feature Request] Support Custom Backends for Toolkits #3554
• [BUG] the current terminal toolkit break if the container doesnot exist #3429

👤 Suggested Assignees

• Wendong-Fan
• Michaelsqj
• libowen2121
• lightaime
• JINO-ROHIT

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!