'omni' 검색 결과

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reproducing a first-run setup problem
• Inspecting menus in a narrow terminal
• Checking help text and command visibility

Use when configuring OmniStudio at the org level: enabling Standard Runtime, selecting the Runtime Namespace, assigning Permission Set Licenses, toggling feature settings, and granting Experience Cloud community access. Trigger keywords: OmniStudio Settings, Standard OmniStudio Runtime, managed package runtime, runtime namespace, OmniStudio Permission Set, OmniStudio PSL. NOT for moving an org off the vlocity namespace — use omnistudio/vlocity-to-native-omnistudio-migration. NOT for deciding whether to adopt OmniStudio — use architect/omnistudio-vs-standard-decision.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Connect AI agents to OmniRoute through MCP, a protocol for accessing tools. Use tools for request routing, memory, cache, providers, and audits, with three connection methods and permission scopes that control which operations are available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Connect Claude Desktop or an editor to OmniRoute
• Inspect and explain request routing
• Add and search stored memories

Set up and check OmniRoute authentication for API access and dashboard sessions. Use Bearer credentials for remote requests, manage login cookies, inspect authentication status, and configure OIDC, a standard for signing in through an identity provider.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up API key authentication for OmniRoute
• Logging in to and out of dashboard sessions
• Checking authentication status and CSRF tokens

Create and manage secure tunnels that make OmniRoute accessible over the internet. Use ngrok, Cloudflare Tunnel, or a custom tunnel to share access with remote agents and automated build and test pipelines.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Expose OmniRoute through a secure tunnel
• Share access with remote agents
• Connect CI pipelines to OmniRoute

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a minimal Omnigent agent
• Configuring an agent with web search
• Adding shell access or MCP tool connections

Run concurrent Omnigent conversations with real hosts and runners while replacing the LLM with a zero-latency mock. Read the generated report to explain response-time distributions, throughput, and failures, helping assess Omnigent's own processing overhead.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Measuring performance with concurrent hosts
• Studying latency as conversation history grows
• Comparing throughput and failures under load

Configure Codex CLI to connect through OmniRoute on Linux, macOS, or Windows. The workflow detects the operating system and shell, creates configuration files and seven profiles, sets environment variables, and verifies the setup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Connect Codex CLI to OmniRoute
• Set up Codex across different operating systems
• Create seven named configuration profiles

Test Omnigent’s native Pi integration using the real terminal interface and a local server. Verify messages sent through the web or API, recorded replies, interruption, session resumption, authentication, and model settings to investigate integration problems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking message delivery from the web or API to Pi
• Verifying replies appear in the server transcript
• Testing interruption, resumption, and tool policies

Use this skill to gather, document, and validate OmniScript flow design requirements before development begins — covering screen layout requirements, branching logic, data source requirements, and user journey mapping. Trigger keywords: OmniScript requirements, OmniScript BA, OmniScript screen design, OmniScript user journey, OmniScript branching requirements. NOT for building the OmniScript or moving logic into an Integration Procedure — use omnistudio/omniscript-design-patterns. NOT for FlexCard requirements — use admin/flexcard-requirements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing message delivery from the web interface to agy
• Checking terminal output against mirrored session replies
• Verifying permission requests and interruption

Synchronize OmniRoute configuration, provider connections, and settings with cloud storage. Manage authentication for the cloud worker, a remote service, along with its credentials and remote backup destinations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Synchronize OmniRoute settings with cloud storage
• Initialize cloud synchronization
• Update cloud worker credentials

Use the command line to send tasks to OmniRoute's A2A server, which supports communication between agents. Inspect execution history and logs, monitor or cancel tasks, and interactively test the JSON-RPC 2.0 communication protocol.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check server status and available skills
• Invoke a skill with JSON input
• Inspect task history and logs

Test Omnigent’s GitHub Copilot SDK integration on a live local server. Build test agents, run real conversations, and inspect authentication, model selection, tool connections, policy enforcement, and leftover processes to investigate integration failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking Copilot authentication with a real conversation
• Testing model selection and tool connections
• Verifying sub-agent dispatch and policy enforcement

Verify Omnigent behavior through real user actions in an isolated environment. Use a feature map to cover relevant web, terminal, and CLI entry points, preserving recordings and other evidence for bug reproductions and fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reproducing a user-facing Omnigent bug
• Comparing behavior before and after a fix
• Checking coverage across web, terminal, and CLI entry points

Look up how to configure and organize Omnigent agents. Use examples to choose an executor, the agent's runtime, arrange instructions and skills, add local tools or external services, and define specialized child agents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check agent directory layout and config.yaml settings
• Choose an executor and harness
• Add skills, custom tools, or MCP services

Manage AI service connections in OmniRoute through its API. Add, update, remove, and test connections, maintain API keys and sign-in credentials, and inspect usage metrics and connection health.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding or updating AI service connections
• Renewing expired sign-in credentials
• Testing multiple connections together

Query OmniRoute through A2A, a protocol for communication between agents. Get provider and model recommendations, check remaining quotas, find providers with required features, estimate request costs, and review system health.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find a provider and model for a prompt
• Check remaining provider or account quotas
• Find providers with required features

Set up OmniRoute and manage its command-line configuration. Inspect and validate tool settings, manage environment variables, check for updates, and control automatic startup using commands that support both interactive and unattended setup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up a provider and default model
• Inspecting and validating CLI tool settings
• Checking or changing environment variables

Check OmniRoute server health, component status, and live metrics from the command line. Filter alerts or watch a refreshing dashboard to see provider status and circuit breakers, which interrupt requests when failures occur.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking server health
• Reviewing component alerts
• Watching live metrics and provider status

Manage AI provider connections from the terminal. List configured services, test connections individually or together, rotate credentials, and inspect usage metrics. Validate local configuration without contacting providers when checking its structure.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test all active provider connections together
• Validate configuration without external requests
• Rotate provider credentials and manage OmniRoute API keys

Manage command-line tools connected to OmniRoute through its API. Inspect tool status, read or change settings, manage Codex profiles and backups, and invoke tool plugins for automation tasks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing settings across connected tools
• Managing Codex profiles
• Checking tool status and logs

Check and control OmniRoute’s MCP server, which connects agents to tools. Inspect tool permission scopes, enable or restart the server, and invoke tools with JSON arguments from the command line.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check the MCP server’s operating status
• Enable, disable, or restart the server
• Inspect permission scopes for a tool

Generate video clips from text descriptions or reference images through multiple API services. Compare available providers by cost and task needs, choose aspect ratios, track generation progress, and refine existing clips through conversational editing with Gemini Omni.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generating clips from written scene descriptions
• Animating a product photo
• Creating vertical videos for social media