omnigent

Test polly's coordination of coding agents using a scripted mock language model and live command-line tools. Check startup, task dispatch, safety rules, parallel delegation, and whether real agents make appropriate orchestration decisions.

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

• Reproducing polly orchestration bugs
• Checking safety rules with a mock language model
• Verifying delegation and cross-review with real agents

Investigate a reported bug before choosing a fix. Trace the actual failure, test competing explanations, and examine design history so the proposed change preserves intended behavior and clearly separates verified findings from unresolved assumptions.

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

• Reconstructing the conditions of a reported bug
• Distinguishing a symptom from its underlying cause
• Checking intended behavior in tests and history

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

Build and run Omnigent’s server and Postgres together with Docker Compose on a laptop or existing Docker host. Use the supplied configuration and troubleshooting guidance to rebuild images, investigate startup problems, or adapt deployment to another platform.

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

• Running Omnigent locally with Postgres
• Starting the stack on an existing VPS or EC2 host
• Investigating startup and web interface problems

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.

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

• Write release notes covering changes since the last tag
• Summarize pull requests merged during a selected period
• Highlight breaking changes before an upgrade

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

Prepare a structured JSON handoff for bug fixes or pull request reviews. Capture outcomes, test evidence, change impact, publication status, and remaining work so the next person or workflow can understand what is complete and what remains.

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

• Handing off a completed bug fix
• Recording an existing pull request review
• Documenting unresolved checks and remaining work

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

Commit a validated bug fix and follow the selected publication path: keep it local, prepare it for a CI publisher, or open a pull request. Organize the description, regression test evidence, and handoff details for review.

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

• Keeping a validated fix in a local commit
• Preparing a pull request description and test evidence
• Handing publication over to a CI workflow

Review code changes with an independent agent from a different model provider. After tests pass, check a fixed diff against acceptance criteria, send blocking issues back to the implementer, and repeat until review passes.

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

• Get an independent review from another model provider
• Check a pull request against acceptance criteria
• Turn blocking findings into concrete fix tasks

Prepare a bug-fixing run by recovering reproduction details and tests, checking the workspace, and finding existing fixes. Select the appropriate workflow for a reproduction session, CI run, bug ticket, or requested PR changes.

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

• Recover reproduction tests from a session or CI run
• Check the workspace before starting a bug fix
• Find existing fixes before choosing an approach

Create upgrade guides for changes that make existing code or settings stop working. The skill checks differences and history, then provides specific steps, copyable before-and-after examples, and any available options for postponing the upgrade.

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

• Documenting an API rename
• Explaining removed flags or changed defaults
• Showing code before and after an upgrade

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

Investigate a bug's root cause, implement a focused repair, and verify the same behavior before and after the change. Select lasting regression tests, preserve reproduction evidence, and record the corrected user journey when possible.

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

• Investigating and fixing a bug without an existing candidate PR
• Proving a repair with failing-then-passing tests
• Consolidating regression checks into existing tests

Research questions on the web and produce a report with source links. Read full pages, check important claims against independent sources, and clearly distinguish supported findings from uncertain evidence or disagreements.

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

• Research a question that requires current information
• Cross-check important claims across independent sources
• Compare conflicting accounts and explain uncertainty

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.

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

• Test authentication and real Gemini responses
• Verify tool connections and sub-agent delegation
• Investigate model selection failures

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

Audit recovered bug reproduction tests before writing a fix or reviewing a pull request. Check that assertions reflect intended behavior, establish a valid failure on unfixed code, and verify the same test passes after the fix.

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

• Checking recovered reproduction tests before fixing a bug
• Validating test evidence for a pull request
• Rewriting weak assertions around actual behavior