tsujin

To manage growing demand for Claude we're adjusting our 5 hour session limits for free/Pro/Max subs during peak hours. Your weekly limits remain unchanged. During weekdays between 5am–11am PT / 1pm–7pm GMT, you'll move through your 5-hour session limits faster than before.

To manage growing demand for Claude we're adjusting our 5 hour session limits for free/Pro/Max subs during peak hours. Your weekly limits remain unchanged. During weekdays between 5am–11am PT / 1pm–7pm GMT, you'll move through your 5-hour session limits faster than before.

Features in OpenCode itself will be internal plugins and can be activated/deactivated at runtime. Same as external plugins. This will allow for reloading plugins at runtime. Trying to tweak the DX a little more. Almost ready to go.

OpenCode is about to get more powerful with remote sandboxes I showed a brief demo before, but here's a much more in-depth demo. it's not hard to add basic support for a remote env, but handling all the edge cases like when a remote env gets deleted is difficult. especially if care about good UX You never want to lose session data. so the choices are: run the session in your env, but run all tool calls remotely. that's too complex and painful. The other way is to just let the full session run remotely, but sync back all the session data in your env. We chose this path: we built a syncing system which logs all events in a way that we can always recreate your entire session. That means the remote env could get destroyed, but we can easily restore it. it also opens up other interesting ideas which we'll be exploring

i'm making an oxlint rule to ban vi.mock