'smoke-test' 검색 결과

Check a gbrain installation after a restart or when services seem broken. It tests key components, repairs some local problems, checks OpenClaw when installed, and records results, with support for custom test scripts.

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

• Check services after a machine or container restart
• Investigate problems with a gbrain installation
• Check OpenClaw services when installed

Create a dedicated test project linked to the current worktree and check Agent Builder through APIs and browser interactions. It covers agent and skill management, permissions, defaults, and related features, with selectable test sections.

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

• Validate an Agent Builder feature branch before review
• Check role-based permissions and authentication
• Test agent and skill management through APIs and the UI

Create a Mastra project at a specified version and check its Studio in Chrome. Test page loading, agent chat, tool execution, and workflows, then report passed and failed checks, encountered errors, and screenshots.

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

• Checking a newly created Mastra project
• Testing initialization with a specified version or package manager
• Checking Studio chat, tools, and workflows

Check opencode commands, HTTP server behavior, lifecycle events, and terminal startup with purpose-built scripts. Find stored sessions by ID, title, or scoped message searches, and export conversations as JSON for further inspection.

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

• Check CLI commands and HTTP server health
• Observe lifecycle events associated with plugin hooks
• Check terminal startup and keyboard input

Prepare the local environment for the Maestro smoke-test suite — verify tooling, select a device, collect the APK if needed, validate the .env file by variable name only, then hand the user the exact lab-store CLI command to run or run it on request.

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

임시 터널과 외부 도구가 필요 없는 작업으로 로컬 에이전트 API와 원격 샌드박스의 통신을 검증하고, 웹 앱의 기존 API 연결 복원까지 확인합니다.

• 로컬 API의 전체 통신 흐름 검증
• 전송 후 멈춘 작업의 원인 조사
• 게이트웨이 통신의 로컬 API 도달 확인

Test community plugin imports in OpenDesign from folders, zip archives, GitHub subpaths, or marketplace entries. Produce a compact receipt showing the plugin name, source type, detected files, and user notes for inspection.

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

• Testing imports from a local folder or zip archive
• Checking GitHub subpath or marketplace imports
• Inspecting installation, application, and source details

Check a DeerFlow installation from code updates through deployment and basic service checks. Supports local and Docker setups, verifies frontend pages and API health, and produces a report with results and troubleshooting recommendations.

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

• Checking DeerFlow after installation
• Verifying startup after a code update
• Checking a Docker deployment

Test omo Codex Light edition in an isolated environment using real Codex and a local mock model. Verify installation, plugin hooks, and terminal startup, with captured evidence and no calls to a real model API.

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

• Verify installation and config.toml changes in isolation
• Confirm plugin hooks run during a real Codex turn
• Check terminal interface startup

Test the Senpi adapter and task engine against the real senpi binary in an isolated environment. Check task and team behavior, record evidence in a consistent location, and verify that the existing agent directory remains untouched.

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

• Verify adapter behavior after code changes
• Test task execution and team recovery
• Check that skills reach child tasks

Run diffusers generation pipelines from a terminal and save their outputs. Inspect accepted inputs without downloading model weights, apply LoRA adapters during generation, run remotely through HF Jobs, and inspect software and GPU environment details.

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

• Running one-off generation or batch jobs from a terminal
• Checking a new model's basic operation
• Inspecting accepted inputs before running a pipeline

Run smoke tests, or basic operational checks, for Mastra projects locally or in staging and production. Verify Studio screens, agents, tools, workflows, traces, and memory, then report results, blockers, and skipped checks.

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

• Checking a local Mastra project before release
• Testing Studio and server deployments in the cloud
• Running targeted checks for agents or traces

Run OpenShell’s Release Canary checks to verify that published development packages and Helm charts install and support basic sandbox operations. Use workflow logs and local Kubernetes reproduction steps to investigate failures before a public release.

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

• Checking published development artifacts before release
• Testing changes to the Release Canary workflow
• Investigating installation or sandbox test failures

Run MNN checks and regression tests on a host computer or Android device, with stage summaries and failure logs. A separate workflow benchmarks LLM prompt processing and token generation on real iPhones and iPads, including branch comparisons.

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

• Run static checks and host regression tests
• Verify selected backends on an Android device
• Benchmark LLM speed and compare branches on iPhone or iPad

Evaluate a driving agent on CARLA Leaderboard routes after checking the required setup. Select routes and repetitions, save driving scores and infractions, record runs, and resume interrupted evaluations from a saved checkpoint.

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

• Smoke-test a Leaderboard setup on one route
• Evaluate an agent across validation routes
• Resume an evaluation after a crash

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 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

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

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

Test Omnigent’s Cursor SDK integration against a live local server. Build test agents, run real conversations, and check authentication, model selection, and tool connections while investigating empty responses or bridge processes left after shutdown.

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

• Test Cursor authentication and real responses
• Verify file operations and sub-agent delegation
• Investigate invalid models and empty output

Configure how Dynamo routes requests to workers, then check model discovery and a chat response. Supports local and Kubernetes setups, including routing based on cached model data, with clear commands, results, and limitations.

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

• Start a local Dynamo frontend
• Change routing settings on Kubernetes
• Check model discovery and a chat response

Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after BB feature changes or when asked to verify or smoke-test BB. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected recipes and platform prerequisites.

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

Start or patch Dynamo router modes and run router endpoint smoke checks. Use for round-robin, KV-aware, least-loaded, or device-aware routing setup; use recipe-runner for recipe deployment and troubleshoot for failure diagnosis.

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

Use this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS, checking per-device per-library capabilities, scoping output to a specific PCIe address, or capturing a side-effect-free capability snapshot for debug or install smoke-test. Trigger even when the user does not explicitly mention "doca_caps" or "capabilities print tool" — typical implicit phrasings include "what does DOCA actually see on this box", "is my BlueField PF visible to DOCA", "is Flow available on my RHEL host", "enumerate VF representors for pf0", "doca_caps: command not found", or "empty output for RDMA, is the tool broken". Refuse and route elsewhere for DOCA installation (doca-setup owns it; never walk the steps), library-internal capability matrices (Flow pipe creation, RDMA verbs features), streaming telemetry / DTS, or modifying the shipped binary.

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