@GooglePlayDev New signup fails with "Precondition check failed" because my old dev account (ID 8279745294448592464, closed for inactivity 2024) is still attached to my Google account. All support URLs 404 or loop back to the closed Console. Need a working ticket link 🙏
As my timeline is having an "agents are the future" moment, let me share the agent failure I have been fighting in my spare time over the past two days.
I am adding minimal ssh -J support to sshpiper. It is entirely reflective, in the sense that sshpiper will only act as a jump box for hosts it can already reach. (I am implementing this primarily to help in testing another piece of software in the https://t.co/rCiZyr11L3 stack, though it will become a product feature at some point.)
With a careful three-paragraph description, unsurprisingly, Claude Code can one-shot basic -J support. So can Codex. I tried it out manually and it works well, and passed all of my auth tests.
However, I then plugged it into a larger test suite as a replacement for direct ssh connections. There is a test where the jump box mode does not clean up properly, with the ssh -J variation hanging while the direct ssh connection would exit.
No amount of prompting Opus 4.5 or Codex 5.1 max so far has fixed this. I have reimplemented support multiple times, watched both agents flail with various attempts at socket closing / half-closing / context cancelation / cleanup logic. I have carefully guided the models through generating simpler reproduction tests and let them spin on the problem. So far I have spent about $400 and two hours of my time trying to make this work.
And so here we have a clear limitation of agents today. Perhaps a year from now they will be able to solve this. But today, if the limits of your ability to program are to find exotic ways to ask an agent to work, you could not build this. You would have to find some inferior workaround. While I have not yet found the hours to tackle this task manually, I feel confident I can implement this sort of TCP socket handling.
I am generally of the opinion that agents are great. Most of the code I have created over the last year has been via an agent. I would go so far as to say that "agents are the future" is wrong because agents are the present, avoiding them makes as much sense to me as refusing to read compiler error messages. But if you want maximum flexibility, the ability to build anything you can imagine, you still need a human programmer in reserve, who can recognize the limits is not your imagination but your model's intellectual capability, and switch to doing it by hand. Ignore that limit only if your problem space allows it.
@PR0GRAMMERHUM0R design patterns are all about injecting function into another function, because function cannot be passed as parameter or assign function to var