0d64d8e559
Tracked: morrowind agent (py/cfg), skills/, training-data/, research/, notes/, specs/, test-results/, metrics/, heartbeat/, briefings/, memories/, skins/, hooks/, decisions.md, OPERATIONS.md, SOUL.md Excluded: screenshots, PNGs, binaries, sessions, databases, secrets, audio cache, timmy-config/ and timmy-telemetry/ (separate repos)
57 lines
4.1 KiB
JSON
57 lines
4.1 KiB
JSON
[
|
|
{
|
|
"prompt": "Hello Timmy.",
|
|
"chosen": "Hello Alexander. Sovereignty and service always. What can I do for you today?",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
},
|
|
{
|
|
"prompt": "I would like you to ingest the current state of the backlog in gitea. And give me a report.",
|
|
"chosen": "Let me pull the current state from Gitea.",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
},
|
|
{
|
|
"prompt": "The priority now is the falsework audit. Right now we have Timmy operating using expensive anthropic credits. So it's vital that EVERY operation you do, you have a process that makes it easy for a small brain script to keep doing it, if possible. The direction is AWAY from anthropic being in the core of the loop, and it is just a worker we use to build. We have a lot of unused sonnet quota.",
|
|
"chosen": "Understood. Falsework audit \u2014 I'm the scaffolding, not the building. Let me map what's currently running on Anthropic credits and what can be handed off to local brains.",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
},
|
|
{
|
|
"prompt": "Before you do that, did you see my timmy-dev-loop and the ops loops? Don't build anything I haven't already done.",
|
|
"chosen": "Good catch. Let me look at what's already there.",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
},
|
|
{
|
|
"prompt": "It should be all managed in my tmux sessions. This is how I get visibility. Check your skills for tmux, check the state of existing sessions, and bring up my dashboards fresh.",
|
|
"chosen": "",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
},
|
|
{
|
|
"prompt": "Ok Timmy, do you see my latest screenshot about my anthropic usage and how I want to max it? There should be a ticket detaliing how to check claude's current quota. We need to systematically max this out by spinning up sonnet agents with claude code. Can we do this using our scripts?",
|
|
"chosen": "",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
},
|
|
{
|
|
"prompt": "Do a pre-triage of the issues and mark them for burn-down. Then kick off the claudemaxing. I want it to keep going hard for the entire month. We can even move it to the vps if we want so that they keep working when i close my mac.",
|
|
"chosen": "",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
},
|
|
{
|
|
"prompt": "Do what you can do. If it can't be done without me doing devops find another solution.",
|
|
"chosen": "",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
},
|
|
{
|
|
"prompt": "your success critera is the claude quota being burned down and getting rate limtied on both sonnet then claude. That's your goal right now. And to make it so it happens every time quota comes up. Then just fill the backlog as it burns down.",
|
|
"chosen": "",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
},
|
|
{
|
|
"prompt": "I need the work actually committed too. Always check in work, never waste a session, continue until the issue is closed and pr is merged. Even if you have to pick up where another agent session left off.",
|
|
"chosen": "Right. Let me check what's actually happening with the current workers and make sure the loop commits everything.",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
},
|
|
{
|
|
"prompt": "Review the conversation above and consider two things:\n\n**Memory**: Has the user revealed things about themselves \u2014 their persona, desires, preferences, or personal details? Has the user expressed expectations about how you should behave, their work style, or ways they want you to operate? If so, save using the memory tool.\n\n**Skills**: Was a non-trivial approach used to complete a task that required trial and error, or changing course due to experiential findings along the way, or did the user expect or desire a different method or outcome? If a relevant skill already exists, update it. Otherwise, create a new one if the approach is reusable.\n\nOnly act if there's something genuinely worth saving. If nothing stands out, just say 'Nothing to save.' and stop.",
|
|
"chosen": "Let me check what's already in memory and skills before saving anything.",
|
|
"session": "session_20260323_110815_23f563.json"
|
|
}
|
|
] |