Changelog
What changed and when, newest first. Only dates that can be checked are listed.
Site
Changes to sshgjr.com, taken from the site's own history.
- Added the Company, Terms of use and Changelog pages, plus a shared footer, a sitemap and basic organisation data for search engines.
- Company page: the founder's GitHub profile.
- Switched off the bot check on the demos. One switch turns it back on.
- Added “Watch the system work”: three recorded replays of real runs, played back step by step from static files. Personal details removed.
- Added a Korean/English toggle in the header. It remembers your choice, follows your browser language the first time, and the demos answer in the chosen language.
- The demos now run on the Claude API (live mode) instead of fixed sample responses.
- Added the founder name and the September 2026 timeline.
- Published sshgjr.com: one static page, the two demos and the privacy note.
Product
Feature-level milestones of the product itself, which isn't public. Dates come from my recorded design decisions.
- Telegram stall ping tuned: a session waiting on me with no approval card now sends one Telegram message after 15 minutes.
- Questions that wait on me are delivered to Telegram as cards with answer buttons.
- Approvals with risk cards. When a permission check refuses an action, the session asks for a yes/no card showing the exact command, why it was blocked, whether it can be undone and a low/medium/high risk rating.
- Cache-aware lifecycle. A cold session is replaced instead of woken, a rule shaped by the first 48-hour measurement of cache writes (the token-waste measurement).
- Approval relay. The secretariat shows the pending approvals and presses or types my confirmed answer.
- Cleaner. Once the secretariat session's context fills up, it saves what matters and replaces the session with a fresh one.
- Secretariat. The session I talk to; it routes work to the front desks.
- Several front desks can run side by side.
- Usage gates. How many workers may run in parallel depends on the 5-hour usage.
- Front desk. One session takes requests and hands the code work to workers in fresh git worktrees.
- First code of the product (private repository).