Repository navigation
Releases
Releases · Vensus137/Coreness-DSH
v0.11.3
🐛 Fixes
- The Agent Team card works on DSH 0.2.2 again: its two prompt switches find the rewritten team policy, and a team that is switched off reads as off rather than as a missing sentence.
- The Agent Team card no longer shows a member ceiling; its two prompt switches stay as they were.
- Qoder's search switch, turned off on DSH 0.2.2, stops pinning an older search provider and returns to the platform's default DeepSeek search.
🎨 Experience
- On macOS, a drag across the MCP confirmation mask no longer moves the application window.
v0.11.2
🐛 Fixes
- Removing an MCP server works on DSH 0.2.2: the row leaves the servers file and stays gone after a restart.
- Saving an OAuth reference on an MCP row no longer answers an error after the row has been written.
- The Agent Team card shows the ceiling in force on DSH 0.2.2 instead of an empty value.
🎨 Experience
- The panel's menu keeps its hover highlight on DSH 0.2.2.
- A page fetch checks the proxy first: a proxy that fails the check leaves the fetch direct, and a fetch failing through a reachable proxy is reported as the error, not retried.
v0.11.1
✨ Features
- A second switch, "Proxy all traffic", sends every request the harness itself makes through the stored proxy — model, search, page fetch, MCP connections, the market — at once, with no restart.
- The two proxy switches are independent: turning the whole traffic off gives page fetching its own switch back as it was left, with nothing to re-toggle.
- The proxy card's URL line stands above both switches now, and the all-traffic switch sits under the page-fetch one.
🐛 Fixes
- A proxy that refuses a tunnel reads as a network failure now: the model call is retried through it, and a page fetch with its own switch on repeats directly.
v0.11.0
✨ Features
- Page fetches can use the product's own fetch: a browser identity and up to 200 000 characters instead of the platform fetch's 100 000.
- A page fetch can go through an HTTP or HTTPS proxy first and be repeated directly when the proxy fails on the network.
- The proxy card checks the stored proxy and answers Works, Refused or No answer without fetching any page.
- Both switches stand on the General page as cards of their own, beside the Agent team card.
🐛 Fixes
- A profile whose page-fetch selection names no provider gets the platform's fetch back when the app starts.
- A profile whose search selection was left empty gets the platform's search back when the app starts.
- The Qoder web switch selects search only now, so turning it off can no longer break page fetching.
🎨 Experience
- The proxy URL stays visible in its field, so it never has to be retyped.
- The proxy card's verdicts are one word each, and the reason behind a verdict goes to the console.
v0.10.4
v0.10.3
✨ Features
- The page opens with a picture of the panel and its MCP section, and shows the limiter and the Agent team card as they look — before anything is installed.
- An animation shows an MCP server being switched on, its tools appearing and the counter moving.
- The page says that every part is its own plugin, so a profile carries only the parts it uses.
🐛 Fixes
- The install section no longer says a machine without git can install it: the address is a git repository, and the install reads it with git.
- The update path is described as it works: a newer version is reported in Discover, and the update is taking the plugin off and adding it again.
🎨 Experience
- The page is much shorter: the two closing sections are gone, and the terminal detail stands behind a collapsed block.
- One Telegram badge under the title replaces a contact block, and the page ends with what the package contains.
v0.10.2
✨ Features
- Installs on a DeepSeek Harness older than 0.2.1-rc.2, which the previous release refused — no Harness version is refused now.
🐛 Fixes
- The install page asks for no DeepSeek Harness version: the plugin installs on any, and no version check leaves it out.
🎨 Experience
- The
spendtool and the per-request cost ledger are gone; tokens, model and ending stay in the platform's own session log. - A
qoder-requests.ndjsonfile already in the harness home is no longer written or read; delete it when convenient. - The
journalandjournal_notetools and the journal's route are gone; the platform's own session log remains the record of requests. - The journal's file already in the harness home is no longer written or read; delete it when convenient.
- The product's files now live under
$DSH_HOME/coreness/qoder/— the machine id and the vendor's effort menus — not in the root of the harness home. - The machine id is generated again at the new path, so Qoder sees a new device id for this machine.
- The copies a previous version left under
$DSH_HOME/qoder/are not read, moved or deleted.
v0.9.0
v0.8.4
✨ Features
- The chat's reasoning-effort menu offers the levels the model's vendor publishes, beside the product's own switch-off, instead of only the platform's three words.
🐛 Fixes
- The menu reads as one ladder from off to the hardest level, so a weaker level no longer stands below a stronger one.
🎨 Experience
- The Agent team card names the act that ends it: it asks to enable Agent Teams instead of reporting the team as not mounted.
v0.8.3
🐛 Fixes
- The credits popup uses the product's own type: its title is as large as other cards' titles, the names of its sections at a name's size, and nothing in it is bolder than the rest.
- The panel opens with what it read last time in place — its two checks, its field and its Save — and a press made while the read still runs is answered; a first open shows those controls waiting.
🎨 Experience
- The panel's title no longer waits for a read to show the version: the tag stands in the first frame of an open.