terminal-agent-benchmark

Run and maintain Con's terminal-agent benchmark against a live app session. Use when validating con-cli, SSH workspace reuse, tmux awareness, agent-target preparation, or when collecting benchmark evidence for regressions and release notes.

Ir a la instalación

Repositorio: nowledge-co/con-terminal
Última actividad en el origen: 30 de abril de 2026 a las 15:25
Idioma detectado de SKILL.md: inglés
Estrellas: 556
Forks: 44

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/nowledge-co/con-terminal --skill terminal-agent-benchmark

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

release

Run and verify Con beta, dev, and stable releases without publishing incomplete artifacts.

2026-08-27

con-cli-e2e

Validate Con's local socket control plane against a real running app session, and write/run con-test integration tests. Use when testing con-cli, the Unix socket API, pane control, tmux control, in-session agent calls, or when writing E2E test cases in crates/con-test/testdata/.

2026-05-08

changelog-release-notes

Maintain Con's CHANGELOG.md and release notes. Use when updating changelog entries, preparing a beta/dev release, reviewing PR release-note coverage, or ensuring contributor PR credit is present.

2026-05-07

Ver todos los de este repositorio

Terminal Agent Benchmark

Use this skill when you need to evaluate Con as a terminal-native agent, not just compile it.

Primary references:

Default workflow

Confirm a live app session and socket exist.

Run the strict benchmark:

python3 benchmarks/terminal-agent/run.py --suite strict

If provider setup is present, run:

CON_BENCH_ENABLE_AGENT=1 python3 benchmarks/terminal-agent/run.py --suite all

Prefer a built-in profile when one matches the workflow:

python3 benchmarks/terminal-agent/run.py --list-profiles
python3 benchmarks/terminal-agent/run.py --profile basic-local-shell
CON_BENCH_ENABLE_AGENT=1 python3 benchmarks/terminal-agent/run.py --profile basic-local-codex --suite all

Use starter profiles for quick regression checks and operator profiles for richer coding, SSH maintenance, or tmux dev-loop evaluation.

python3 benchmarks/terminal-agent/run.py --profile operator-local-codex-devloop --suite operator
python3 benchmarks/terminal-agent/run.py --profile operator-local-claude-devloop --suite operator
python3 benchmarks/terminal-agent/run.py --profile operator-local-opencode-devloop --suite operator
python3 benchmarks/terminal-agent/run.py --profile operator-ssh-dual-host-maintenance --suite operator
python3 benchmarks/terminal-agent/run.py --profile operator-ssh-tmux-devloop --suite operator

For SSH/tmux changes, run the relevant playbook under benchmarks/terminal-agent/playbooks/.

Save the JSON record under .context/benchmarks/ and cite it in your report.

If the run is an operator benchmark, score it with:

python3 benchmarks/terminal-agent/score.py --profile ... --record ... --score ...

Generate a trend report when comparing many runs:

python3 benchmarks/terminal-agent/report.py

Rules

Prefer pane_id over pane_index when following up on benchmark findings.

Keep benchmark control on the existing panes.* API unless the benchmark explicitly targets pane-local surfaces. Surface support is additive and should not change the built-in agent's pane/tool contract.

Do not treat playbook observations as strict pass/fail evidence unless the behavior is actually deterministic.

If a scenario depends on host setup, say so explicitly.

Keep operator playbooks safe-by-default. Prefer read-only checks first, and treat destructive or privileged steps as explicit branches.

If a benchmark reveals a product limit, document the limit instead of hiding it behind a softer assertion.

Operator suites intentionally serialize agent ask turns. If a tab already has a pending agent request, let the runner wait and reuse the same tab instead of opening a parallel benchmark against it.