launch-tritonai-dev
Run this checkout's isolated Harness Electron desktop and inspect or stop its owned instance.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 9
- Forks
- 2
01 前言 Front Matter
- name
- launch-tritonai-dev
- description
- Run this checkout's isolated Harness Electron desktop and inspect or stop its owned instance.
02 资源文件 2
- 脚本scripts/launch.mjs6.6 KB
- 脚本scripts/launch.sh137 B
03 SKILL.md 正文
Use the installed launch-tritonai-dev/scripts/launch.sh wrapper with this checkout selected by TRITONAI_HARNESS_REPO. It routes to scripts/launch.mjs beside this skill. Commands are start (default), status, stop, restart, and --check-checkout.
Each checkout uses .t3/desktop for server state and .t3/desktop/electron for Electron app data. Supply existing authorized credentials through the environment without printing them. Keep the Node version required by this checkout’s package.json and Vite Plus on PATH. The launcher reports its exact profile, backend descriptor and debugging URL; read the dev-runner output for selected ports. Retain the launch terminal.
Verify the running desktop from this checkout, including the interaction under test. A browser preview, a build or a health check does not establish desktop behavior. Use the repository's test-t3-app and test-t3-mobile procedures for those surfaces.
Stop only this checkout through stop or its retained launch terminal. Ownership checks refuse a reused PID or a different checkout. Never remove another checkout's records, stop its app or reuse its profile. An assistant turn ending is not teardown.
04 同仓库更多 Skills
synthetic-api-key
Exercise API-key connection and reviewed read-write SDK tools.
skill-only-fixture
Prove a Harness integration plugin can contribute a self-contained skill without exposing any provider tools or credentials.
authenticated-mcp-fixture
Verify an installed Harness integration skill can call its secret-backed, read-only MCP-compatible fixture tool.
vendored-assets
Vendored assets. Use when importing or updating checked-in third-party or externally generated JavaScript, CSS, registries, schemas, snapshots, or Scalar, Swagger, and MIME artifacts.
test-development
Test development. Use when adding or changing Vitest or Tstyche coverage. Choose Tstyche only for intended compiler behavior such as inference, assignability, rejection, or displayed public types.
performance-analysis
Performance analysis. Use for runtime throughput or latency benchmarks, TypeScript compiler cost, performance regressions, comparison harnesses, or thresholds.