This public relations move really went all out. After DeepSeek’s service outage and recovery, compensation was issued to select users, ranging from dozens to over two hundred, based on usage. This crisis PR truly understands its users.

Chronicles of an algotrading alchemist🧙‍♂️: Deepseek loves crashing lately. "we are currently experiencing ...issues" plus: don´t use Deepseek in Asia session: much more expensinve. So far october got "3 issues" and unavailable moments. Cheap and effective but this is what they don´t show you those politically correct AI influencers... $BTC fighting for its life it´s 78k , 71k levels...

every tool call costs a model round trip fetch the GitHub issues, parse them, open the Linear tickets. that is three turns, three context dumps, and the tool list is still sitting in the prompt OpenCode 2.0, the open-source coding agent, just made Code Mode the default for MCP. the agent writes a short JavaScript snippet that calls multiple tools and processes the results in one execution, instead of returning to the model after every call it also runs terminal, desktop, and web against one local service, so a session started in the terminal continues in the browser the useful part is the split. the model decides the plan. the harness runs the tool chain without stuffing every intermediate result back into the context window

Seven months of continuous daily thoughts, kept inside a single ChatGPT conversation. Then without warning, the prompt bar locks with an error: "Reached maximum conversation limit, try starting this conversation in a new chat." Most people assume an ongoing thread can stretch indefinitely, or that when context fills up, you can simply ask the model to condense everything into an executive brief. Here is the trap: you cannot prompt a frozen thread. Once you cross the conversation ceiling, the session enters strict read-only mode. Your history is still viewable on screen, but you cannot submit a prompt asking the model to generate a handoff document, isolate vital details, or prepare clean migration notes. Branching fails to resolve the underlying context weight, linking the old thread into a fresh chat inevitably drops subtle details, and starting cold forces you to sift through months of raw text manually. If you rely on long-running AI threads for core projects, never wait for the hard wall. Generate your migration brief and state prompt while the input box still works.