For People Confused About Session Credit Limits

It's actually not the session limit (i.e. maximum number of ACUs that can be consumed in a session), but the limit at which devin would stop working after each user message (i.e. devin works till it either finishes his job or reaches the session limit ACUs). This is so that Devin doesn't get stuck in a loop of doing the same action (or same set of actions) over and over again for a long time leading to unnecessarily high ACU consumption. Once Devin hits the session limit, he will go to sleep and must be woken up again to resume. Keep in mind that waking him up from a state like this can affect performance if done too often in a single session.

NOTE: This does not reset the overall session ACU consumption