Claude Console 0.1.3

Claude Console 0.1.3

The setup profile release: an optional, reversible way to set Claude Code up the way
the console's author works, plus recovery tools, a written privacy guarantee and fixes
to update and rollback. Everything below is new since 0.1.2.

New: the setup profile (optional, beta)

• 22 modules with 292 items, from session hand-offs and the /done ritual to commit
  identity hooks, test tiers, size budgets and a lessons library. Each item says what it
  does, why it is on, what it needs and what it usually goes with. Nothing is on until
  you choose it. Reference: docs/profile.md.
• A setup wizard with two paths: Use Remus3's exact current settings (the quick
  path for experienced users) or Custom setup. Every screen shows Step x of y,
  has Back and lets you switch paths; skipped inputs turn off only the modules that
  need them. It opens as a full page over the console (never a pop-up you must
  answer), and Skip for now leaves it at any step before Apply without writing
  anything.
• A review step before anything is enabled, with the as-is note and the list of
  safeguards, and one checkbox to continue.
• A profile browser (... menu, Setup profile, or Settings > Setup profile) to
  view, enable, disable and edit every item, with a diff and a dry-run review before
  apply.
• claude-console profile list | view | diff | apply | enable | disable | edit | revert | uninstall | verify | status | update. Apply is a dry run unless you add
  --apply --yes; each apply backs up what it touches, reads every write back and
  rolls back on the first failure; revert restores byte for byte.
• Machine changes (user environment variables, keys stored with Windows DPAPI,
  scheduled tasks named ClaudeProfile-*, local git settings) each have a backup and
  an undo record. The profile never commits, pushes or starts a background run itself.
• Updates to the author's settings: quick-path users see the list of changes and take
  them in one step; custom users get them merged into their own choices, with clashes
  listed.

New: adopt an existing project

Copy first, then a report of every file and line per rule, yes or no per module and per
change, a function check that runs your project's own tests, build and start on both
the original and the copy, promote only after you confirm "works", and removal of the
original only as a later, separate step to the Recycle Bin or a zip. Guide:
docs/adopt.md.

New: recovery and help

• Stop everything (... menu or claude-console stop-all): ends the processes the
  console started by recorded process id, pauses the profile's tasks, turns its hooks
  off and unsets the background-run kill switch. resume turns it all back on.
• recover.ps1, a standalone Windows PowerShell script that does the same with the
  console down (-WhatIf, -Stop, -DisableHooks, -PauseTasks, -Resume,
  -Revert last, -Prompt). It ships in the release zip and as a release asset.
• Report a problem / claude-console crash-report: a scrubbed report you read in
  full first, then open as a GitHub issue, hand to a local Claude pane, or save.
• Get help in the browser / claude-console recover-prompt: a self-contained
  recovery text on the clipboard and claude.ai opened, for when Claude itself is broken.
• Manual steps for the worst case: docs/recovery.md.

Privacy

The README now states it plainly: nothing is sent to the author or anyone else, and
there is no telemetry. The only network calls are the update check and download, and
actions you start. Tests enforce it: a static scan of every shipped script against an
allow list (installer/egress.json), a runtime test that refuses every non-loopback
call, and a release test in Windows Sandbox with networking off. Details:
docs/privacy.md.

Fixed

• Update and rollback refresh the version shown in Apps & features.
• The console is stopped before an update swaps its program folder.
• Two regular expressions that could take very long on crafted input (code scanning
  alerts) now run in linear time.

Project

• The repository is now Remus3/Claude-Console; the command stays claude-console.
• Security policy, contributing guide, code of conduct, issue and pull request
  templates (including a crash report form) and a CI workflow on Windows / Node 24.
• A rewritten README with screenshots of the console.

Update

From 0.1.0, 0.1.1 or 0.1.2: claude-console update --yes, the Update badge in the
console, or run the installer again:

irm https://github.com/Remus3/Claude-Console/releases/latest/download/install.ps1 | iex

The setup profile stays off after the update until you open it.

Assets

File	What
install.ps1	the one-command installer
claude-console-0.1.3.zip	the release (one claude-console-0.1.3/ folder with MANIFEST.json)
recover.ps1	the standalone recovery script
SHA256SUMS.txt	SHA-256 of the zip, install.ps1 and recover.ps1

Claude Console 0.1.2

Claude Console 0.1.2

A fix release for uninstall.

Fixed

• claude-console uninstall --purge removed everything but exited 1 and printed
  "The system cannot find the path specified." twice. The launcher and the install
  folder were removed on a fixed 3 s timer, sometimes while the command was still
  running. They are now removed by a small cleanup script in %TEMP% that first waits
  for the command (and the claude-console.cmd that ran it) to exit, then deletes
  itself. Plain uninstall and uninstall --purge both finish, print their result and
  exit 0 before anything is removed.
• claude-console.cmd passes the command's exact exit code on (0.1.1 reported every
  failure as 1).

Update

From 0.1.0 or 0.1.1: claude-console update --yes, the Update badge in the console, or
run the installer again:

irm https://github.com/Remus3/claude-console/releases/latest/download/install.ps1 | iex

Assets

File	What
install.ps1	the one-command installer
claude-console-0.1.2.zip	the release (one claude-console-0.1.2/ folder with MANIFEST.json)
SHA256SUMS.txt	SHA-256 of the zip and of install.ps1

Claude Console 0.1.1

Claude Console 0.1.1

A fix release for stop and uninstall.

Fixed

• claude-console stop said "stopped" while the server process that opened the app
  window kept running: the server stopped listening but waited on the window's open
  connections. The server now ends every WebSocket and HTTP connection when it shuts
  down and exits after a 3 s grace period at most.
• stop now waits for the server process itself to exit, not only for port 7800 to
  close. It reports a failure when the process is still running after the timeout
  (--timeout S, default 10 s); stop --force ends it.
• claude-console uninstall printed EPERM for the app folder, left it behind and
  still exited 0. It now stops the server (and any leftover server of an older version)
  first, retries the removal, and exits non-zero with one uninstall incomplete: ...
  line naming what is left whenever anything remains. It never reports success while
  files remain.
• claude-console.cmd passes the exit code on (it returned 0 to PowerShell after a
  failed command).
• An update restart waits for the old server process to exit before it starts the new
  version.

Update

From 0.1.0: claude-console update --yes, the Update badge in the console, or run the
installer again:

irm https://github.com/Remus3/claude-console/releases/latest/download/install.ps1 | iex

Assets

File	What
install.ps1	the one-command installer
claude-console-0.1.1.zip	the release (one claude-console-0.1.1/ folder with MANIFEST.json)
SHA256SUMS.txt	SHA-256 of the zip and of install.ps1

Claude Console 0.1.0

Claude Console 0.1.0

First public release.

Install

irm https://github.com/Remus3/claude-console/releases/latest/download/install.ps1 | iex

Windows 10 / 11. The installer adds Node.js LTS and Git when they are missing, checks
the download against SHA256SUMS.txt, installs to
%LOCALAPPDATA%\Programs\claude-console and starts the console. Rather not run a
remote script? Download install.ps1, the zip and SHA256SUMS.txt, read the script,
then run powershell -ExecutionPolicy Bypass -File .\install.ps1 -Zip .\claude-console-0.1.0.zip.
Claude panes need the Claude Code CLI (irm https://claude.ai/install.ps1 | iex).

What is in it

• Tiled terminal panes for Claude Code sessions and shells (node-pty + xterm.js) in an
  app window, local only (127.0.0.1, per-start token).
• A project list of the git repos on your drive, with branch, changes, hand-off and
  progress files.
• Settings, layouts and sidebar groups saved on your computer.
• Health & cleanup, a scheduled-task view, a usage panel.
• Update-aware install: a daily release check with an Update badge, 3-way merge of your
  local changes, backup and self-test before switching, rollback, repair and fresh
  reinstall, uninstall (Apps & features or claude-console uninstall).

Assets

File	What
install.ps1	the one-command installer
claude-console-0.1.0.zip	the release (one claude-console-0.1.0/ folder with MANIFEST.json)
SHA256SUMS.txt	SHA-256 of the zip and of install.ps1