This is interesting, ideally with checkpointing and other such mechanisms, the long term session recovery will improve.
What does need to be seen is how well the agent works with the recovered context. In certain cases when I was trying to do this locally (using a custom setup), the agent just skimmed through the context and skipped over its own findings before the session crashed.
I do like the code mode though, agents indeed are good at that. In an 80 repo code migration, claude code figured out that the task is going to become repetitive and the patterns are identified, so it wrote a shell script to automate the migration, and itself acting just as a progress monitor
But in reality, the real cost of engineering teams grow as the sub organizations and teams continue to make short term decisions, optimizing for the next immediate win.
More common so in larger organizations than smaller ones
What does need to be seen is how well the agent works with the recovered context. In certain cases when I was trying to do this locally (using a custom setup), the agent just skimmed through the context and skipped over its own findings before the session crashed.
I do like the code mode though, agents indeed are good at that. In an 80 repo code migration, claude code figured out that the task is going to become repetitive and the patterns are identified, so it wrote a shell script to automate the migration, and itself acting just as a progress monitor
reply