Menú
Drives Gantry agent-chat tests through the local Control API session path and captures assistant responses. Use when testing an agent response, permission prompt, skill behavior, or runtime chat flow without needing Telegram UI rendering.
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.
Basado en la clasificación ocupacional SOC
| name | agent-chat-test |
| description | Drives Gantry agent-chat tests through the local Control API session path and captures assistant responses. Use when testing an agent response, permission prompt, skill behavior, or runtime chat flow without needing Telegram UI rendering. |
Use this skill when the goal is to send a test message to a Gantry agent and
inspect the runtime response. Prefer this over telegram-agent-loop unless the
thing being tested is specifically Telegram UI rendering, Telegram buttons, or
visible Telegram topic behavior.
node scripts/agent_chat_test.mjs --fresh "Ask a short status question and reply in one sentence."
The script sends through Gantry's app/session Control API. This exercises the real session enqueue path, runtime queue, permission handling, and outbound session events without direct Postgres writes.
npm run build
node dist/cli/index.js service restart
node dist/cli/index.js status
node scripts/agent_chat_test.mjs --fresh "Use the LinkedIn posting skill to draft a harmless test post, then stop before publishing."
Session identifies the app session used for the test.Conversation identifies the app conversation.Accepted message proves the message was durably accepted.node dist/cli/index.js status
tail -n 200 ~/gantry/logs/gantry.log
--conversation-id codex-test-name to reuse a stable test conversation.--fresh to avoid stale session context by appending a timestamp.--thread-id <id> only when testing thread-scoped behavior.--json when another script needs structured output.--timeout-ms <ms> to shorten or lengthen the wait, up to 300000 ms.telegram-agent-loop for those cases.Operate the Symphony Forge harness: start tasks, save approved plans, record decisions, assumptions, and client sign-off, harvest the docs/context inbox, check gate status, and review proposed skills. Invoke when the user says "start a task", "save this plan", "record a decision", "harvest context", "is this PR ready", "harness status", "what now", "create a new app", "set up a new project", "show me progress", "show the board", "review the plan", or "/forge".
Operate the Symphony Forge harness: start tasks, save approved plans, record decisions, assumptions, and client sign-off, harvest the docs/context inbox, check gate status, and review proposed skills. Invoke when the user says "start a task", "save this plan", "record a decision", "harvest context", "is this PR ready", "harness status", "what now", "show me progress", "show the board", "review the plan", "create a new app", "set up a new project", or "/forge".
Gantry self-administration reference for current host runtime operations: CLI commands, settings.yaml runtime settings, .env credential keys, agent management, scheduler tools, memory tools, browser tools, diagnostics, and service control. Use when asked to manage Gantry itself.
Use for folder movement, layer boundaries, and domain/application/runtime/adapters refactors in Gantry.
Use for tools, permissions, risky actions, sandbox, browser, and execution safety changes in Gantry.
Use for LLM, channel, browser, sandbox, credential, and external provider adapter changes in Gantry.