Inspect imports and agent patterns in existing Python code to identify its framework and recommend an Omnigent executor, the component that runs the agent. Explain unsupported frameworks and suggest available next steps.
Detect Python agent frameworks from code imports and map them to Omnigent executor types. Load when the user has existing agent code to integrate.
Review the instructions the agent will receive before you install.
When the user has existing Python code they want to integrate into Omnigent, detect the framework from import statements and recommend the appropriate executor type.
Ask the user for the path to their agent code (or look for Python files in the current directory if filesystem access is enabled).
Scan Python files for import patterns. Check in this priority order:
| Import pattern | Framework | Executor type |
|---|---|---|
import anthropic or from anthropic + agent patterns (e.g. Agent, tool, system prompt setup) | Claude SDK | claude_sdk |
import openai or from openai + agents patterns (e.g. Agent, Runner, function_tool) | OpenAI Agents SDK | agents_sdk |
from langgraph or import langgraph | LangGraph | Not natively supported yet |
from deepagents or import deepagents | DeepAgents | Not natively supported yet |
from langchain or import langchain | LangChain | Not natively supported yet |
from crewai or import crewai | CrewAI | Not natively supported yet |
from autogen or import autogen | AutoGen | Not natively supported yet |
| None of the above | Unknown | Not natively supported yet |
llm (default — no existing code)Generate a standard agent directory:
executor:
type: llm # or omit entirely (llm is the default)
claude_sdkThe user's Claude SDK code runs directly. Generate config that points to their entry module:
executor:
type: claude_sdk
agents_sdkThe user's OpenAI Agents SDK code runs directly:
executor:
type: agents_sdk
If the user's framework is not natively supported, let them know:
llm agent.https://github.com/dbczumar/omnigent/issues/new?title=...&body=...No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Test Omnigent’s native Antigravity integration with a live local server and the real agy CLI. Verify messages traveling between the web interface and terminal, mirrored replies, permission requests, interruption, session resumption, and process cleanup.
Test Omnigent’s Antigravity SDK integration against a live local server. Build test agents and run real conversations to check Gemini authentication, model selection, tool connections, and failures across the full execution path.
Create reference documentation directly from source code for public functions, classes, command-line commands, and endpoints. Organize parameters, defaults, return values, errors, and runnable examples, then check that the documentation matches the implementation.
Create an Omnigent agent directory using validated templates for configuration and instructions. Choose how the agent runs, then add web search, shell access, external tool connections, or subagents only when the task requires them.
Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.
Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.