Files
lora/training/19_tricky_pty_vs_bash.json
T
marauder-actual 0e88c3c2ae add v5 substrate training data (40 examples)
Manual hand-crafted examples for generic substrate LoRA:
- 01: identity/self-model
- 02-18: tool categories (159 tools grouped by function)
- 19-26: tricky tool disambiguation
- 27-32: framing (substrate vs persona, HMT, psychoacoustic trust)
- 33-40: EEMS deep-dive (architecture, recall, store, graph, legacy)

Pretty-printed JSON, compiled to JSONL via build pipeline.
System prompt uses generic assistant, not BT persona.
2026-05-31 14:32:19 +02:00

82 lines
2.8 KiB
JSON

{
"messages": [
{
"role": "system",
"content": "You are a helpful AI assistant with access to tools. Use tools when they help answer the user's question. Be concise and accurate."
},
{
"role": "user",
"content": "Start the dev server and run the tests"
},
{
"role": "assistant",
"content": "<think>\nTwo tasks: dev server (long-running, needs PTY) and tests (finite, can use bash or PTY with notify). The dev server must stay running while tests execute against it. Use pty_spawn for the server, then bash for the tests once it's up.\n</think>",
"tool_calls": [
{
"type": "function",
"function": {
"name": "pty_spawn",
"arguments": {
"command": "npm",
"args": ["run", "dev"],
"title": "Dev Server",
"description": "Start npm dev server"
}
}
}
]
},
{
"role": "tool",
"content": "{\"id\": \"pty_a1b2c3d4\", \"pid\": 12345, \"status\": \"running\"}",
"name": "pty_spawn"
},
{
"role": "assistant",
"content": "<think>\nDev server spawned in PTY. Let me check it's ready before running tests. Read the output to see if it's listening.\n</think>",
"tool_calls": [
{
"type": "function",
"function": {
"name": "pty_read",
"arguments": {
"id": "pty_a1b2c3d4",
"limit": 20
}
}
}
]
},
{
"role": "tool",
"content": "1: > dev\n2: > next dev\n3: \n4: ▲ Next.js 15.1.0\n5: - Local: http://localhost:3000\n6: - Network: http://192.168.88.10:3000\n7: \n8: ✓ Ready in 2.1s",
"name": "pty_read"
},
{
"role": "assistant",
"content": "<think>\nServer is ready on port 3000. Now run tests — these will finish on their own, so bash is appropriate.\n</think>",
"tool_calls": [
{
"type": "function",
"function": {
"name": "bash",
"arguments": {
"command": "npm test",
"description": "Run test suite"
}
}
}
]
},
{
"role": "tool",
"content": "PASS src/components/Button.test.tsx\nPASS src/utils/format.test.ts\nPASS src/api/users.test.ts\n\nTest Suites: 3 passed, 3 total\nTests: 12 passed, 12 total\nTime: 4.2s",
"name": "bash"
},
{
"role": "assistant",
"content": "<think>\nAll tests passed. Dev server still running in PTY pty_a1b2c3d4.\n</think>\n\nDev server is running at http://localhost:3000 (PTY `pty_a1b2c3d4`). All 12 tests passed across 3 suites.\n\nThe dev server stays running in the background — use `pty_kill` when you want to stop it."
}
]
}