Oraicle-Agent
Turn any Google-ADK Agent into a Root Agent - instantly.
Oraicle-Agent is a groundbreaking Python library that extends the Google Agent Development Kit (Google-ADK), enabling any agent to become a root_agent dynamically, without hacks, forks, or duplicated apps.
This unlocks a new architectural paradigm for multi-agent systems:
- Multiple conversational entrypoints
- Direct chat with sub-agents
- True Agent-to-Agent (A2A) orchestration
- Seamless deployment on Vertex AI Agent Engine
🚀 Why Oraicle-Agent exists
Google-ADK assumes:
- One
root_agentper application - Sub-agents can’t be direct entrypoints
- One conversational domain per deployment
Oraicle-Agent breaks this limitation - intentionally and cleanly.
With Oraicle-Agent, any agent can become the root of a conversation, while still participating in a larger A2A system.
🔥 This is not a hack.
🔥 This is not a fork.
🔥 This is a new abstraction layer.
✨ What makes Oraicle-Agent unique?
✅ Dynamic Root Agents
Choose at runtime which agent owns the conversation.
✅ Direct Sub-Agent Chat
Users can talk directly to a specialized agent (teacher, assistant, expert) without losing context isolation.
✅ A2A-First Architecture
Root agents orchestrate other agents, while still being callable as standalone conversational entities.
✅ Google-ADK & Vertex AI Compatible
Works with:
adk web- ADK loader
- Vertex AI Agent Engine
🧩 The core idea (one line)
Any
Agentcan be aroot_agentif it is explicitly declared as one.
Oraicle-Agent formalizes this idea.
📦 Installation
pip install oraicle
⚡ Quick Start
from oraicle import autoagent
from google.adk.agents import Agent
history_teacher = Agent(
name="history_teacher",
model="gemini-2.0-flash",
instruction="You are a history teacher."
)
autoagent(history_teacher)
☁️ Deploying to Vertex AI Agent Engine
from app.sub_agents.history_teacher.agent import history_teacher
🔧 Using Tools with Oraicle-Agent
Oraicle-Agent provides automatic runtime discovery of tools, allowing sub-agents to use tools without importing directly from app.tools.
This ensures:
- No PYTHONPATH hacks
- No custom bootstrap commands
- Full compatibility with adk web ./sub_agents
- Clean, scalable architecture
📁 Recommended project structure
app/
├── tools/
│ ├── student_exam.py
│ ├── register_student_grades.py
│ └── any_new_tool.py
│
└── sub_agents/
└── history_teacher/
├── agent.py
└── prompt.py
Each tool should live inside app/tools and expose public functions
(optionally using __all__).
✅ Importing tools inside sub-agents (correct way)
Instead of importing tools directly from app.tools, always import them from oraicle.tools.
❌ Do NOT do this
from app.tools.student_exam import student_exam
from app.tools.register_student_grades import register_student_grades
✅ Do this
from oraicle.tools import student_exam, register_student_grades
Oraicle-Agent will automatically discover and load all tools inside app/tools at runtime.
⚡ Example: Sub-agent using tools
from google.adk.agents import Agent
from oraicle import autoagent
from oraicle.tools import student_exam, register_student_grades
from .prompt import AGENT_PROMPT
history_teacher = Agent(
name="history_teacher",
model="gemini-2.0-flash-lite",
instruction=AGENT_PROMPT,
tools=[
student_exam,
register_student_grades,
],
)
autoagent(history_teacher)
No additional configuration is required.
🚀 Running locally with ADK
Oraicle-Agent works with the default ADK command, no bootstrap needed:
adk web ./sub_agents
All sub-agents will:
- Be discovered automatically
- Act as independent root_agents
- Have full access to shared tools
- Maintain isolated conversational contexts
🧠 Why this matters
This design turns app/tools into a runtime tool registry, not a static import dependency.
You get:
- True plug-and-play tools
- Zero coupling between app and sub-agents
- A clean A2A + Tooling architecture
- Production-safe execution (local & Vertex AI)
📄 License
MIT License © 2026
Built with 🤖 for the GenAI community.
Metadata
Release files for oraicle 3.4.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 | |
|---|---|---|---|---|
| oraicle-3.4.0.tar.gz | 10.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| oraicle-3.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.2 kB
Release files / oraicle-3.4.0.tar.gz
| Download URL | oraicle-3.4.0.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
27732a20f327237ad4b292906ccf13abc6ae5d4c869fbd27c04307814ea53fb4
|
|
BLAKE2b-256 checksum How to use checksums |
23d380ab686a759a4d6f7e18de5fab28d41a7b16049b1ae2b0f3d477be2328dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / oraicle-3.4.0-py3-none-any.whl
| Download URL | oraicle-3.4.0-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9666dd59e0e973e60637746b4881f947ca61fe11199660ef67d51043f3c699ff
|
|
BLAKE2b-256 checksum How to use checksums |
93ec2e3e19ce5cd2fd29c09a8e208023e04e17b3fc9ae21a67b3a9647ecb4d26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for oraicle 3.4.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.