3 ms·

Resuming sessions after more than 1 hour is a very common workflow that many teams are following. It will be great if this is considered as an expected behaviou

by bobkb 6mo ago

Resuming sessions after more than 1 hour is a very common workflow that many teams are following. It will be great if this is considered as an expected behaviour and design the UX around it. Perhaps you are not realising the fact that Claude code has replaced the shells people were using (ie now bash is replaced with a Claude code session).

trinsic2 6mo ago
I think thats a bad idea. It seems like expecting to have a prompt open like this, accumulating context puts a load on the back end. Its one of those things that is a bad habit. Like trying to maintain open tabs in a browser as a way to keep your work flow up to date when what you really should be doing is taking notes of your process and working from there. I have project folders/files and memory stored for each session, when I come back to my projects the context is drawn from the memory files and the status that were saved in my project md files. Create a better workflow for your self and your teams and do it the right way. Quick expect the prompt to store everything for you. For the Claude team. If you havent already, I'd recommend you create some best practices for people that don't know any better, otherwise people are going to expect things to be a certain way and its going to cause a lot of friction when people cant do what the expect to be able to do.
- kiratp 6mo ago
  Agents making forward progress hours apart is an expected pattern and inference engines are being adapted to serve that purpose well. It’s hard to do it without killing performance and requires engineering in the DC to have fast access to SSDs etc. Disclosure: work on ai@msft. Opinions my own.
- troupo 6mo ago
  > I think thats a bad idea. It seems like expecting to have a prompt open like this, accumulating context puts a load on the back end Let's see what Boris Cherny himself and other Anthropic vibe-coders say about this: https://x.com/bcherny/status/2044847849662505288 https://x.com/bcherny/status/2044847849662505288 Opus 4.7 loves doing complex, long-running tasks like deep research, refactoring code, building complex features, iterating until it hits a performance benchmark. https://x.com/bcherny/status/2007179858435281082 https://x.com/bcherny/status/2007179858435281082 For very long-running tasks, I will either (a) prompt Claude to verify its work with a background agent when it's done... so Claude can cook without being blocked on me. https://x.com/trq212/status/2033097354560393727 https://x.com/trq212/status/2033097354560393727 Opus 4.6 is incredibly reliable at long running tasks https://x.com/trq212/status/2032518424375734646 https://x.com/trq212/status/2032518424375734646 The long context window means fewer compactions and longer-running sessions. I've found myself starting new sessions much less frequently with 1 million context. https://x.com/trq212/status/2032245598754324968 https://x.com/trq212/status/2032245598754324968 I used to be a religious /clear user, but doing much less now, imo 4.6 is quite good across long context windows --- I could go on
gib444 6mo ago
> Resuming sessions after more than 1 hour is a very common workflow that many teams are following Yeah it's called lunch!

by bobkb 6mo ago

trinsic2 6mo ago

I think thats a bad idea. It seems like expecting to have a prompt open like this, accumulating context puts a load on the back end. Its one of those things that is a bad habit. Like trying to maintain open tabs in a browser as a way to keep your work flow up to date when what you really should be doing is taking notes of your process and working from there. I have project folders/files and memory stored for each session, when I come back to my projects the context is drawn from the memory files and the status that were saved in my project md files. Create a better workflow for your self and your teams and do it the right way. Quick expect the prompt to store everything for you. For the Claude team. If you havent already, I'd recommend you create some best practices for people that don't know any better, otherwise people are going to expect things to be a certain way and its going to cause a lot of friction when people cant do what the expect to be able to do.

kiratp 6mo ago
Agents making forward progress hours apart is an expected pattern and inference engines are being adapted to serve that purpose well. It’s hard to do it without killing performance and requires engineering in the DC to have fast access to SSDs etc. Disclosure: work on ai@msft. Opinions my own.
troupo 6mo ago
> I think thats a bad idea. It seems like expecting to have a prompt open like this, accumulating context puts a load on the back end Let's see what Boris Cherny himself and other Anthropic vibe-coders say about this: https://x.com/bcherny/status/2044847849662505288 https://x.com/bcherny/status/2044847849662505288 Opus 4.7 loves doing complex, long-running tasks like deep research, refactoring code, building complex features, iterating until it hits a performance benchmark. https://x.com/bcherny/status/2007179858435281082 https://x.com/bcherny/status/2007179858435281082 For very long-running tasks, I will either (a) prompt Claude to verify its work with a background agent when it's done... so Claude can cook without being blocked on me. https://x.com/trq212/status/2033097354560393727 https://x.com/trq212/status/2033097354560393727 Opus 4.6 is incredibly reliable at long running tasks https://x.com/trq212/status/2032518424375734646 https://x.com/trq212/status/2032518424375734646 The long context window means fewer compactions and longer-running sessions. I've found myself starting new sessions much less frequently with 1 million context. https://x.com/trq212/status/2032245598754324968 https://x.com/trq212/status/2032245598754324968 I used to be a religious /clear user, but doing much less now, imo 4.6 is quite good across long context windows --- I could go on

gib444 6mo ago

> Resuming sessions after more than 1 hour is a very common workflow that many teams are following Yeah it's called lunch!