{"full_name":"totec448-spec/chat-on-steroids","owner":"totec448-spec","name":"chat-on-steroids","url":"https://github.com/totec448-spec/chat-on-steroids","description":"Cross-platform local MCP capabilities for ChatGPT with Chrome integration, Goal, Compact & Resume, and durable multi-agent workflows.","homepage":null,"topics":[],"language":"TypeScript","license":"MIT","avatar":"https://avatars.githubusercontent.com/u/227782719?v=4","created_at":"2026-08-22T14:16:24Z","pushed_at":"2026-11-10T05:36:52Z","metrics":{"stars":5146,"forks":667,"watchers":11,"issues":570,"prs":1541,"releases":51,"issues_open":null,"issues_closed":null,"prs_open":null,"prs_closed":null,"prs_merged":null,"discussions":0},"growth":{"day":{"stars":0,"forks":0,"base_day":"2026-11-09"}},"history":{"dates":["2026-11-09","2026-11-10"],"stars":[5146,5146],"forks":[667,667],"watchers":[11,11],"issues_open":[null,null],"prs_open":[null,null]},"boards":{"new":133},"same_owner":[],"issues":[{"number":482,"title":"Roadmap: feature ideas in one place","comments":80,"created_at":"2026-09-27T06:12:34Z"},{"number":2085,"title":"2.1.50: GPT-6 High appears as Medium during long Loop session","comments":15,"created_at":"2026-11-06T17:30:29Z"},{"number":1882,"title":"2.1.46: Loop/Normal selector mismatch during stalled chat after #1803","comments":13,"created_at":"2026-10-27T11:29:12Z"},{"number":1721,"title":"82 features coming from my fork, ten PRs at a time","comments":11,"created_at":"2026-10-21T00:40:30Z"},{"number":2029,"title":"Tool calls lose exact conversation attribution across turns, causing stale plans and tool rejections","comments":10,"created_at":"2026-11-02T05:04:56Z"},{"number":2005,"title":"[2.1.49] Historical ImageGen gallery misses previews and appends old messages with new timestamps","comments":10,"created_at":"2026-11-01T13:24:13Z"},{"number":1807,"title":"CoS v2.1.45: Core Tunnel sign-in failed despite successful standalone tunnel-client startup","comments":10,"created_at":"2026-10-23T16:58:31Z"},{"number":1878,"title":"2.1.46 / Windows 10: existing-chat messages time out before browser pickup","comments":6,"created_at":"2026-10-27T02:04:44Z"}],"discussions":[],"latest_release":{"name":"2.1.50 Move chats between projects, and chats that keep going","tag":"v2.1.50","published_at":"2026-11-03T06:52:17Z","body":"## 2.1.50 Move chats between projects, and chats that keep going\n\nYou can now move a chat into another project by dragging it or from its menu, with Undo. Long chats keep going in more situations: when a step is not picked up, the app keeps trying, tells you, and lets you continue with one click. The browser extension now updates itself even while long chats run, and very long chats no longer slow the app down.\n\n### 👉 After updating\n\n- Nothing to do. The browser extension updates itself. A chat that is still answering delays that by at most 30 minutes; a tool call or a message being sent still finishes first.\n\n### ✨ New\n\n- **Move chats between projects.** Drag a chat onto a project, or onto one of its groups, or use **Move to project** in the chat's menu. A notice says where it went and offers **Undo**. Chat lists also show **Today**, **Yesterday** and earlier date headings. The move happens only in the app; a chat linked to a ChatGPT Project stays where it is in ChatGPT.\n- **The new project's folder, said once.** After you move a chat into a project, your next message there tells ChatGPT the project's folder once, so it works in the right place.\n- **Continue now and Try now.** When a chat's quick tries run out, the app tells you, also on your phone if you set that up, and the chat's notice has **Continue now** or **Try now** to go on at once.\n- **Continue from the last summary.** When ChatGPT stops serving a chat for good, the app can continue it in a new ChatGPT chat from its last summary, still as one chat in the app.\n\n### 💪 Better\n\n- **Chats keep going.** After its quick tries, the app no longer gives up on a step that nobody picked up. It keeps trying every 15 to 60 minutes and says why a step waits. An automatic Continue that waited too long is sent as an ordinary message.\n- **Fresh turns by default.** When ChatGPT shows only Stop for a long time, the app stops and continues in a fresh turn. This was an experimental option and is now on for everyone; you can still turn it off in Settings.\n- **The extension updates during long runs.** It used to wait until no chat was answering, which in busy setups could mean never.\n- **Big chats stay fast.** In very long chats, the app no longer reads the whole history again and again. An automatic Continue that no longer fits the chat's last question is withdrawn instead of being offered for hours.\n- **Thorough Goal helpers get time.** A Goal or Loop helper set to extra-high or Pro reasoning now gets up to 12 or 20 minutes for its next message instead of timing out after three.\n- **Workers in the right mode.** A worker chat picks its own model before its wake-up message is typed.\n- **Compact chat lists.** Rows in Projects and Chats are tighter, so more chats fit on screen, and the keyboard focus outline is fully visible again. Inbox cards stay as they were.\n- **Chat menus on short windows.** A chat's menu that fit on neither side of its button showed a scrollbar for a few pixels. It now opens whole beside the button.\n- **Plugins, Skills and Pets** say when their list could not be loaded, instead of \"Loading…\" for good.\n- **Layout polish:** the + menu, text fields in Settings and the update card in every language.\n\n### 🛠 Fixed\n\n- **Loop chats that stopped when the helper's message got too long.** The helper was never told the length limit, so in long Loop chats its messages grew until one no longer fit, and every retry failed the same way. It is now told the limit, and after a message that was too long it is asked for a shorter one.\n- **The composer gear was missing on an empty message box.** After a change on ChatGPT's side, the Chat On Steroids gear only appeared once you typed something. It is back on every composer.\n- **Recovery that stopped while a tab was stuck.** A tab stuck in rendering mode could stop the app from recovering any chat. Recovery now goes on, and a chat that needs its tab shown gets it shown once.\n- **The app's own leftover text blocking messages.** When an automa"},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-10T09:35:25Z","history_start":"2026-09-06"}