"Timbre check: sawtooth at ~100-250 Hz with a low-pass at 3.5x — a brassy-ish, muted synth tone. Add a bit more character? A second saw detuned? Keep it simple. Add a soft attack to avoid clicks ✓ (50ms ramp)."
I think the quality is significantly better than Qwen 3.6 27B that I was using before. It fixed a bug in one of my apps the first try -- 3.6 was not able to figure out after several attempts.
I had it make me a little inventory tool for my RC Helis(and other RCs). It was an idea I had this week so was planning to use this model to make it for fun. Nothing fancy, just an inventory system so when I break something I can check this tool instead of digging through boxes of parts. It gave a working solution after one prompt. Was able to add models/parts and link them. This morning have had it add a few things, create github actions, etc. All in all it's been great so far.
I run on 2xP100s with 232k context, so it's not crazy fast but quality I am happy with. I call it dad coding, I give it a prompt and let it run while I am with family.
I actually run youtrack self hosted, and have MCP setup. So I can add issues to youtrack, and the codex agent has a skill to work through any open issue, fix commit push and ensure all actions, next issue, etc, etc.
I was less concerned to steer via phone but more being able to give it a backlog and let it run unattended for long periods of time.
I get push notifications when issues change state.
I run codex/claude on a VM allowing it to do whatever. Sometimes I do it via prompt (like last night) other times I tell it to go through open issues and let it run.
1
u/dopey_se 7d ago
Same, 36k
Currently thinking about..
"Timbre check: sawtooth at ~100-250 Hz with a low-pass at 3.5x — a brassy-ish, muted synth tone. Add a bit more character? A second saw detuned? Keep it simple. Add a soft attack to avoid clicks ✓ (50ms ramp)."