Changelog
November 2026
-
Nov 17: Root Compose runs the platform without the old product selector and defines an off-by-default Static profile. Installer rehearsals for Host and Hack now check sign-in, publishing, restart persistence and older Compose files with locally built images (D4-S7b).
-
Nov 16: Correct the saved-data moving guide: preserve Personal exports until a suitable migration is agreed, enforce one submission per visitor with a unique index, retain shared-state visitor writes, and show the hosted deadline only on hosted installs (R4-S3b review).
-
Nov 16: Publish the guide for moving older saved data to storage and rules. Explain the hosted 17 December switch and operator-configured dates on other installs. The Storage panel shows the local switch time and what happens afterwards; preset-save warnings use a readable UTC date (R4-S3b).
-
Nov 16: Plan-based
migrate-rulesapply and revert refuse unsafe plan files and plans missing the running program’s commit, before changing any resources (R4-S4a). -
Nov 16: Add storage-retirement notice drafts and an operator command that writes private recipient lists without sending mail. Startup reports how many SQLite and key-value resources still use presets. A preset save warns during a configured notice period; no switch date is set and access is unchanged (R4-S3).
-
Nov 16: Installs record their product and refuse startup or migration by another product with exit code 3. Existing installs explicitly record their product once; fresh installers create the schema and product record together (D3-S6a).
-
Nov 15: Simple Host’s API reference, feature list and agent text now describe Simple Host alone. Simple Hack’s API and feature references are generated from shared sources plus its own authored parts, with the same published content (D3-S3).
-
Nov 15: Simple Hack’s skill toolkit (the five skills, the builder and the eight earlier
simple-hack-skills-only-0.2.6to0.2.13downloads) and its landing films moved out of the platform’s embedded files into Simple Hack’s own (D3-S2b). Every Simple Hack address answers as before, each earlier download with the same bytes. A Simple Host install no longer serves the twelve/film/hack-*files (404); no Simple Host page used them. Simple Hack now registers its own file names itself, through one file route, and answers the withdrawn/plugin.zip,/install.shand/install.ps1itself. -
Nov 15: The setup page on a Simple Host install (simple-host.app/setup) offers Small box and Enterprise only. The “Simple Hack on one server” choice and its step list (
/setup/simple-hack.json) are now offered by a Simple Hack install’s own/setup, where the page is unchanged; on Simple Host that file answers 404. Simple Hack’s pages, screens, icons and docs moved out of the platform’s embedded files into the product, so a Simple Host install no longer serves them (for example/hack-ink.css,/og-hack.png,/hack/app.jsnow answer 404 there; no Simple Host page linked to them). Simple Hack installs serve everything as before (D3-S2a). -
Nov 14: Document row rules for SQLite and key-value data, including per-table policies, approval stamps and privacy limits. Update website skills and the Storage guide; file buckets keep presets. Prepared on the R3-S7a branch for activation with R4-S2.
-
Nov 14: Add optional row rules to the storage API and tool schemas, with structured errors and a 256 KiB save limit (R2-S3). The API reference includes these fields; rules saves remain off by default.
-
Nov 14: Add service validation and saving for owner-written row rules, behind
STORAGE_RULES=offby default (R2-S2). API support follows separately. -
Nov 13: Simple Host now offers only its three website skills. Its old hackathons page redirects home, and the organiser guide is no longer served there. Simple Hack keeps its pages and five skills (D2-S11).
-
Nov 13: Limit SQLite table-row work per site, with a short retry response when busy. Recover SQLite panics per request and preserve successful writes if cleanup panics (R1-S3a).
-
Nov 12: Create a site private from the first request, with only you and the viewers you name able to open it. Send access specific and optional viewer emails in the create call; the default stays anyone with the address. Available on Simple Host, including self-hosted installs with visitor sign-in and per-site addresses.
-
Nov 12: Every open site can now be found by search engines. The listed/unlisted switch is renamed List on my profile and only decides whether a site shows on your profile page; it is still off for new sites and every site keeps its current setting. Sites with a passcode or named viewers, offline, taken-down and deleted sites stay out of search engines, and a site’s own robots.txt or noindex is respected. The simple-host.app and simple-hack.app sitemaps now list every open site’s address. Old API and AI-app calls that set visibility keep working.
-
Nov 12: Keep old links working with a root
_redirectsfile, checked on publish and applied after access gates. Plain/faqaddresses servefaq.htmldirectly; directory-only pages keep their trailing slash redirect. -
Nov 12: Simple Hack participants can browse submitted entries from Judging onward. Organisers can show the same submissions on the public event page and custom website feed with a new setting, off by default.
-
Nov 12: Announcements support clickable http(s) addresses, labelled links, bold, bullets and line breaks. Standalone Zoom, Meet, Teams and YouTube links become cards without fetching linked pages. Organisers can preview before posting and pin one announcement, replacing the previous pin; it appears first for participants and judges. Email carries matching HTML buttons and full addresses in plain text.
-
Nov 12: Simple Hack teams can write to the organisers. Any member of a team can send a message from Team to the event’s organisers; it joins the team’s one thread with the organisers’ own messages, which every organiser and teammate can read. Organisers see a line on Home that takes them to the team’s thread, and get an email only if their “Email me when something waits on me” is on. Connected AI apps get
hack_message_organisers. -
Nov 11: Simple Hack co-organiser invitation links are reusable until revoked, replaced, expired or the event ends, and removing a co-organiser revokes the current link.
-
Nov 11: Simple Hack release hack-v0.8.20 for self-hosted installs: no active-event limit by default, more AI apps in the connect steps, and the install fixes from the clean-install test (the example config no longer installs v0.8.0, event time zones work in the containers, support, privacy and Ask settings pass through the config file and survive upgrades, and re-running the installer with the original config works).
-
Nov 11: Simple Hack adds Lovable, Bolt, Cursor and Any other AI app under Other AI apps, keeping Claude, ChatGPT and Claude Code as the primary choices. Simple Host setup also adds Lovable, Bolt and Any other AI app (SIM-435 part 2).
-
Nov 11: Simple Hack defaults to 20 event creations per day and no active-event limit; 0 disables either limit, and admins and EVENT_LIMIT_EXEMPT accounts bypass both.
-
Nov 11: Self-hosted Simple Hack install fixes: use the downloaded release image when no image is set, include time zone data in containers, pass support, privacy and Ask settings through Compose, and explain downloads, password accounts, admin access and upgrades.
-
Nov 11: Simple Hack release hack-v0.8.18 carries everything on main since hack-v0.8.17 (2026-11-05): a redesigned web app with Home as the place to run an event (a checklist for each role and stage, stage changes and publishing results from Home, Your events kept in the side pane, lists and cards that fit the space available); organisers opting in to judge, with one judge list driving assignments, scoring and counts, and judging locks that follow the stage; prizes for 1st, 2nd and 3rd on winner cards; event page Looks (Classic plus five styles); custom event websites that update themselves at every stage; one name per person across events; start and end times on events; two entry presets; notices for judges and organiser messages, with an offer to tell participants at every stage change; a small Ask assistant for organisers that answers from the event and the docs and never changes anything (off on self-hosted installs until you set an OpenAI-compatible endpoint); Account listing Connected AI apps; and the docs at /docs/ with a Self-hosting section. Self-hosted installs show only their own address everywhere. Database migrations 0005 to 0014 apply on upgrade.
-
Nov 11: Simple Hack removes the organiser rubric final step; Ask follows current judging, stage changes, team message delivery and event websites.
-
Nov 10: Simple Hack organisers can set prizes for 1st, 2nd and 3rd in About; winner cards and public feeds show the place and prize, including in winners-only results.
-
Nov 10: Simple Hack Account lists Connected AI apps before collapsible setup steps, with Other AI apps buttons. Home offers Close entries without a deadline; closed entries hide the countdown and show their Website. Schedule names Home, team messages explain delivery, and Settings skips website notifications without a custom website.
-
Nov 10: Simple Hack clarifies event limits, sign-up and judging guidance, hides obsolete checklist tasks, avoids repeat judging notices, shows consistent winner thumbnails and ranks, starts building without a deadline, defaults announcements to Don’t send, clears stage messages, flags short judging coverage, adds member Leave menus, and keeps Schedule open.
-
Nov 10: Simple Hack lists, cards and choice groups fit the available space with the sidebar open; row actions wrap together, and judges see team names beneath entry titles.
-
Nov 10: Custom Simple Hack event websites built from the event recipe update themselves at every stage, including announcements and results.
-
Nov 9: Simple Hack: judging locks follow the stage; stage changes and publishing, including tie order and republishing, live on Home.
-
Nov 9: Simple Hack organisers opt in to judging under Settings → Judging. One judge list drives assignments, scoring and counts; existing scored organisers stay selected. Checklist buttons reach their fixes, information has no button, and starting Judging confirms mode, target, judge names and coverage with links.
-
Nov 9: Simple Hack scoring opens at Judging, which locks judging setup and assigns judges in Automatic mode; returning to Entries closed pauses scoring and unlocks setup.
-
Nov 9: Simple Hack checks every connected app when showing a team’s Website connection, names all apps linked to that team, and explains when an app has not picked a team. Account lists every connected app with its last use and publishing teams, and lets you disconnect each with confirmation.
-
Nov 9: Simple Hack organisers can now Ask from every screen of their event, not just Home, and the assistant explains every organiser setting and option: what it means, what each choice does, when to use it and what happens if, with a link to where it is.
-
Nov 9: Simple Hack organisers can ask a small assistant on Home about their event. It answers in a line or two from the event, its checklist and the docs, links to where to act, and never changes anything. On self-hosted installs it is off until you set an OpenAI-compatible endpoint.
-
Nov 9: A GitHub workflow keeps the docs in step with main: after each check run it rebuilds and checks them, and when they are behind it opens a pull request, with Claude updating the task guides when a rebuild alone is not enough.
-
Nov 9: Simple Hack event pages get a Look setting: Classic plus five whole-page styles (Poster, Confetti, Boardroom, Garden, Terminal), set next to the organiser’s page colour.
-
Nov 9: The docs at /docs/ gained a Self-hosting and Enterprise section built from the current settings and runbooks, a Changelog page, and a plain-Markdown copy of every page at the same address with .md added, for agents reading the docs directly.
-
Nov 9: The docs API and MCP tool references are generated straight from the server’s own route and tool list, replacing the old Swagger page and a hand-kept tools list.
-
Nov 9: Simple Hack entry cards: “Who it’s for” is optional by default in both presets. Events on a preset move with it; custom rules stay as they are.
-
Nov 8: Simple Hack asks before leaving a form with unsaved edits; clean and just-saved forms leave without a prompt.
-
Nov 7: Simple Hack checklist reads batch judging facts by stage, unresolved published ties stay actionable, and rubric acknowledgements use the version displayed. Results edits follow current ties; action links and read-only Home guidance use the event’s actual state and address.
-
Nov 7: Simple Hack checklists number rows across groups, fold blocked earlier work, show No scores yet for empty judge progress, and use compact actions beside phone labels with Read, Check and Score for judges.
-
Nov 7: Simple Hack navigation and checklists: keep declared conflicts removable, refresh Your events, support collapsed switching and read-only admin inspection, correct checklist guidance and destinations, and batch score completion reads.
-
Nov 7: Simple Hack Home now shows the server checklist for each role and stage, with optional-item dismiss/restore and explicit rubric and conflict acknowledgements. Participant entry rows keep their existing appearance and actions (SIM-393, slice 2 UI).
-
Nov 7: Simple Hack keeps Your events in the pane, opens your only current event after bare sign-in, groups organiser activities, and puts event rules in Settings and Tracks on Event page. Organisers can enter their own judge area. Existing setting links keep working; REST and MCP share a navigation map and membership abilities (SIM-388/SIM-393, navigation slice only).
-
Nov 7: Simple Hack checklist server adds role and stage guidance, shared optional-item marks, and explicit rubric/conflict acknowledgements through REST and MCP; participant progress keeps its existing meaning.
-
Nov 7: Fixed the Railway deploy recipe’s visitor-IP trust: Railway’s edge reaches the container over 100.64.0.0/10 (CGNAT), which the Caddyfile’s
trusted_proxiesdid not list, so it trusted neitherX-Forwarded-FornorX-Real-IPand every visitor’s access log and rate limit collapsed onto one address. The recipe now trusts that range and reads the edge’s ownX-Real-IPdirectly, confirmed correct on a real Railway deploy. The docs’ DB_DSN and visitor-IP gotchas, and “What was tested”, now reflect that same live deploy instead of the earlier local-only test. -
Nov 7: Product docs at /docs/ for Host and Hack: task guides built around the Features page, Webhooks, Limits and errors, search, the shared theme, and the API reference at /docs/api/. /docs.html redirects to /docs/, and old links land on the matching page.
-
Nov 6: Web Push joins webhooks and MCP Events as a third delivery kind of the same notification engine, behind a
WEB_PUSH_ACCOUNTSallowlist (forwarded throughcompose.yamland the installer too): the owner and a signed-in visitor may each subscribe their own device site-wide or to one optional resource, with per-resource controls over who it reaches (owner, the row’s owner, both, or none) and whether it shows one named column, validated against the resource’s own schema and an identity/network-word blacklist at save and render time, with the actual value also skipped if it looks like an email or IP; default push text names no row content. Nothing fires back to the actor who made a write — including an owner write stored only so a visitor’s device can be reached, and D1’s own signed-in-on-their-site edits, which still notify an existing webhook/MCP subscriber as before but never push to the owner’s own device — and a visitor’s device only ever receives events about their own data, enforced in the event fan-out itself, re-verified end to end (not just at queueing), rechecked against current named-viewer membership at delivery time, and applied identically to a cursor-based MCP replay, which used to bypass it. The service worker is served at a reserved/v1/push/sw.jspath (proxied everywhere/v1/already is, scoped to/v1/push/rather than root, so it needs no nginx changes and never shadows a site’s own file); subscribe is upsert-safe under concurrent calls (a matching unique index backs the site-locked upsert); the owner can remove any one device, including a visitor’s, not only bulk-revoke a whole site; the visitor/D1 cookie routes require the same CSRF header every other visitor write does. Push subscriptions are deleted on sign-out and SSO-wide revocation (scoped to the signing-out browser’s own session or its whole signed-in-everywhere family, so a different browser survives), named-viewer removal (run inside the removal itself, reaching every caller, not only the dashboard), and moving a site to Recently deleted, and excluded from thelist_notificationsMCP tool and AgentCat’s redaction; push’s own per-site and per-person daily rate limits are reserved together in the send path (an exhausted person never also spends the site’s shared budget); the push endpoint never follows a redirect. -
Nov 6: The owner can now add a row on a
recordsorpersonalSQLite table on behalf of one signed-in visitor — a coach assigning a client’s program, a tutor replying to a student — throughauth.js(table().add(values, {for})), the REST API, or MCP (storage_sql_executewithtable/values), by that visitor’s reference or sign-in email; refused if they have never signed in on that site. The row is marked written by the owner, visible to the visitor, and never triggers the owner’s own webhook subscriptions. A new owner-only pick list (GET .../storage/people,SH.storage.people()) shows the site’s people who have saved data or are named viewers;storage_visitor_emailsnow also resolves emails to a visitor reference. Newget_page_recipetopicpeople. -
Nov 6: Simple Hack now has one name per person instead of one per event. Joining, applying, judging and accepting a co-organiser invite ask for a name only when your account doesn’t already have one, and it’s saved as your account name from then on; if you rename yourself on Account, that new name shows up in every event you’re part of.
-
Nov 6: Simple Hack Event Basics lets organisers set start and end times with the schedule pickers. Empty times mean the start or end of the day; event dates show a time only when one is set.
-
Nov 6: Simple Hack entries have two presets: “Video or website” (the default; a demo video or a website) and “Video, website and code link” (all three). The other presets and the custom option are gone from Entries and from
hack_set_entry_rules; events already set up keep their rules. On a new event, Overview’s first step is “Choose what teams hand in”, then “Open sign-up”. -
Nov 6: MCP refusals that the AgentCat error review found landing in the generic “tool_error” bucket (site-not-found, site-private, site-locked and passcode-locked on the visitor tools,
create_site’s Recently-deleted refusal, andrun_tool’s unknown-tool refusal) now carry their real code and an actionable hint.storage_*tools and the visitor tools now accept each other’s word for a saved-data resource (resource/name), andfind_tools/the page-recipe tools accept a plausible synonym (task/query,kind/topic), without changing the advertised tool schema; an unexpected argument that is not one of those aliases now names the fields the tool actually takes.storage_sql_query,storage_sql_executeandstorage_sql_schemanow say upfront that PRAGMA is not available and to useSELECT name, sql FROM sqlite_schema. -
Nov 6: An AI app that cached an older copy of a tool’s output schema no longer reports a successful call as failed when the result gains a new field;
hack_create_eventhit this afterjudging_ends_atwas added. Schemas stay strict in the tests, and the copy sent to apps accepts extra fields. A new test checks every Simple Hack tool’s real output against its schema. -
Nov 6: Self-hosted installs with password sign-in: the admin Users list shows Reset password only for accounts that have a password. Before, it showed on every account, and using it on a Google or email-code account quietly gave that account a password.
-
Nov 6: The owner page separates Sites, Analytics, and Settings, preserves section links and visibility rules, and keeps AI setup cards and Recently deleted with the site list. Background notification errors stay in their section, and Connected apps distinguishes loading and failed requests from an empty list.
-
Nov 5: Simple Hack notifications grow to cover judges and organiser messages. Judges now get a notice, in the app and by email, when judging opens (with how many teams are in their queue) and a reminder before judging closes while they still have teams left to score, keyed off a new “Judging closes” event field (
judging_ends_at) rather than a schedule row. Organisers can message one or more teams directly (hack_message_team); each team sees it as a notice and by email, with a readable history (hack_get_team_messages/hack_get_my_team_messages). Reminder times are now an event setting organisers control (hack_get_reminder_settings/hack_set_reminder_settings), at most 5 times between 15 minutes and 14 days ahead (default 24 hours and 1 hour), and the same list now drives both participant entry reminders and judge reminders. -
Nov 5: Self-hosted installs of Simple Host and Simple Hack now show only their own address, never ours, across the whole chromed page set (landing, Get started, Account, sign-in, the OAuth Allow page, 404, docs, the footer,
llms.txt, and every MCP tool description including the site-management tools a self-hosted Hack instance also serves): a centralized self-host rewrite pass (chromePage,internal/handler/chrome.go) runs on every page, not just the five previously-enumerated assets, and the footer’s unguardedSimple Hostlink (the one spot<!--sh:hosted-->had been forgotten) is fixed.llms.txtis byte-identical to the baseline text on hosted; a self-hosted install gets its own custom-connector-by-URL wording for Claude, ChatGPT (developer mode) and Claude Code instead, through the same rewrite the other four enumerated assets already used. The 404 page’s “Go to simple-host.app” back-link now names this install’s own domain only when it is genuinely self-hosted; the hosted literal (which also appears, intentionally, on simple-hack.app) is unchanged. New optionalSUPPORT_EMAILandPRIVACY_URLsettings let an install show its own contact and privacy policy instead of ours; unset, a self-hosted install hides the footer’s Privacy/Terms/Report links, replaces everysupport@simple-host.appmailto link and mention (support, terms, privacy, features, pricing, docs, report) with “the person who runs this server”, and shows the same phrase in the OAuth sign-in/Allow steps, which also name the install’s own host. The MCP tool description that namedsimple-hack.app/terms, and the whole site-management tool set’ssimple-host.appmentions (list_sites,create_site,connect_domain, …) that a self-hosted Hack instance serves too, are now instance-aware like the rest of the MCP surface — gated on genuinely self-hosted, not just edition, so the real hosted simple-hack.app keeps its own text. Hosted (simple-host.app, simple-hack.app) is otherwise byte-identical to before this branch. -
Nov 5: Password accounts, redesigned after a second review round: a self sign-up’s typed login is no longer stored as
users.usernameat all — it lives only in a newaccount_passwords.logincolumn (unique there; migration0004-password-login.sqlreplaces the previouslower(username)index, which is dropped) — andusers.usernamebecomes a synthetic, random value instead. This closes, at the root rather than by patching each one, every place that used to treatusers.usernameas a verified address once self sign-up’s login could be anything:visitorEmail(named viewers, savers, visitor sessions, connector/MCP visitor tools), Hack voting identity, sign-in alert mail, Hack notice delivery, and named-viewer sign-in history. The real login comes back asloginon the signup/sign-in response andGET /v1/me, shown by the dashboard, Hack account screen, Hack shell, connector consent page and admin Users page in place ofusername. Admin-created accounts are unchanged (users.username == loginstill, since the admin vouches for the address). Pre-account hijacking is still refused the same way for admin-created password accounts and extended toREVIEW_ACCOUNT_EMAILreviewer sign-in (any password account, not just self-signup) and to an already-linked OAuth identity as defence in depth; a self sign-up’s address and a same-address email-code account now simply coexist as two separate, unrelated accounts rather than needing a refusal at all. -
Nov 5: Simple Hack: every stage change and Publish results offers to tell participants. A short suggested announcement opens for that move; edit it, choose whether to email, then Send or Don’t send.
hack_set_event_stagetells AI apps to offer the same throughhack_post_announcement. -
Nov 5: Simple Hack Get started presents the website and the AI apps as two equal ways in for organisers, participants and judges, with the website clicks written out as fully as the AI prompts.
-
Nov 5: Publishing results now finishes judging.
POST /v1/hack/events/{slug}/results/publishhad no stage check at all, so an organiser Results-screen publish, a direct REST call orhack_publish_resultscould succeed while the event stage was still Judging (or earlier) – the Overview pill and the public page’s “Judging is under way” kicker kept saying Judging even though winners were already out. Publishing now moves the event to the Results stage and locks judging first if it hasn’t reached there yet, the same transition the Overview’s “Finish judging” button performs, so the stage and its words never disagree with what just happened; an already-ended (Archived) event is never reopened, and republishing (e.g. after fixing a disqualified team’s conflict) keeps working at Results or Archived exactly as before. Publishing before entries close (Draft, Open, Building) is refused with 409judging_not_started. No migration. -
Nov 4: Change-own-password review fixes:
POST /v1/me/passwordnow refuses a connector’s OAuth access token (403connector_not_allowed), even one otherwise valid for the REST API, and answers a wrong current password with 403 instead of 401 (the dashboard and Hack account screens read any 401 as an expired key and sign the browser out). The current password is also rejected asbad_credentialswhen it fails the same length check as sign-in, not just on a failed hash match. The Host account page (showcase.html, the normal/<handle>page, not only the apex dashboard) gets the same Password card asindex.html. No migration. -
Nov 4: A signed-in password account can change its own password from the Account page (
POST /v1/me/password, current password plus a new one typed twice in the browser). It is counted on the same sign-in limiters as a wrong password, and never revokes any other key, session or connector token.GET /v1/meaddshas_passwordonly whenPASSWORD_SIGNINis on. No migration. -
Nov 4: Hosted events on Kubernetes can turn on
TEAM_SITE_FLAT_HOSTS(chart valueteamSites.flatHosts, off by default) to serve a team’s site at<team>--<event>.<host>instead of<team>.<event>.<host>, so one wildcard certificate and Ingress rule cover every event and team instead of one per event. Hosted simple-hack.app keeps it off, unchanged. Event and team slugs may no longer contain “–”. -
Nov 4: Password sign-in verifies before locking and checks for concurrent password changes; Argon2 work is limited to two calls. Password sign-up respects country blocks and no longer advertises unused email metadata. Admin discovery failures leave the page usable, and self-hosted Hack pages hide the complete company marketing copy.
-
Nov 4: Self-hosted installs can use username/password accounts, with optional public sign-up and admin-issued temporary passwords. Password sign-in works in the dashboard, Simple Hack and connector consent. Self-hosted pages hide run-your-own-server marketing.
-
Nov 4: Cleanup 5.4: static pages and reviewed skill bundles now live in webassets; event DNS sweep and import jobs move into site services, and the knowledge HTTP routes use an injected store. Routes, responses and asset bytes are unchanged.
-
Nov 4: Admin usage now includes background worker lifecycle and progress reports, with a Background workers table in Overview. HTTP cache and limiter cleanup has explicit cancellation and join ownership; server shutdown drains requests before stopping the worker set.
-
Nov 4:
remove_site_passcodenow needs a fresh yes (Grok bot SIM-350, case 30). The Nov 3 wording fix (below) held for ChatGPT asking for a passcode in chat (case 28), but both ChatGPT and Claude still removed a passcode the moment the person asked for it, reading that request itself as enough consent. The tool now takes aconfirmargument and refuses with an error until it istrue, telling the model to say anyone with the link will be able to open the site once the passcode is gone and get a fresh agreement in the conversation first. No change to the HTTP API (DELETE /v1/sites/{s}/lockis unchanged); any other MCP caller must addconfirm: true. No migration. -
Nov 3: Passcode tool wording (Grok bot SIM-350, cases 28 and 30).
set_site_passcode’s description split “ask the person first” (confirm before calling) from “never ask for the passcode in chat” into two sentences; the combined one let ChatGPT read it as permission to ask the person what passcode they wanted, in chat.remove_site_passcode’s ask-first line now opens the description instead of trailing it, matchinggrant_site_viewer/revoke_site_viewer’s “ASK THE PERSON FIRST” lead. No behaviour change, no migration. -
Nov 2: Classic Simple Hack app removed (cleanup step 2.2, owner-approved).
static/hack-app.html, the single-page classic UI that?ui=classic/cookiesh_hack_ui=classickept reachable, is deleted; the modular app (static/hack/) now serves every signed-in route, including/signin— sign-in by emailed code, link, Google and company OIDC moved there, matching classic’s next= handling (including invite returns to/join,/judge,/organiserand/teamlinks), already-signed-in redirect and SSO handoff with simple-host.app. A leftover?ui=classic,?ui=nextor?ui=newquery parameter, or an oldsh_hack_uicookie, is ignored; the server no longer sets that cookie. A screen whose module fails to load shows a plain reload/Home error card instead of a link back to classic. No migration. -
Nov 2: Migration naming (cleanup step 1.3). New migration files are named
NNNN-what.sqlwith the next free number and apply after the frozen list of existing files (none renamed);migraterefuses a pending numbered file that is not above the newest one already applied (including one recorded by another build), andmigrate -statuslists files in apply order. A new upgrade test builds a hack-v0.8.13 database, migrates it, and compares tables, columns, constraints and indexes with a fresh install; it found thatdb/schema.sqlhad lost theeventsforeign keys onevent_conflictsandevent_scores(fresh installs from hack-v0.8.14 lack them).0001-hack-judging-event-fk.sqlrestores them, removing any score or conflict rows whose event is gone; a no-op on hosted production, which kept them. -
Nov 2: Image matching, fix pass 3c. A check for a site in Recently deleted is postponed while the worker still holds the site’s lock, so a restore can no longer slip in between and leave it waiting an hour. A restore wakes its waiting checks even when the client hangs up after the restore went through. The worker’s first evidence record write keeps a report filed from the admin page, the same as its last write. The docs now say an operator writing into someone else’s files storage is recorded as that operator. Still off until
PHOTODNA_API_KEYis set. No migration. -
Nov 2: Image matching, fix pass 3b. Re-uploading bytes whose check gave up now records the new uploader and upload time. A restore that lands while the worker is postponing a check for the deleted site keeps the check due. A report filed from the admin page while the worker is still finishing a match stays filed in the evidence record. A report with no uploader on record for an event’s site says “uploader not recorded” and never names the event’s holding account. The admin queue counts a check waiting on a deleted site only under
site_deleted, not also as pending or retrying. Still off untilPHOTODNA_API_KEYis set. No migration. -
Nov 2: Image matching, fix pass 3. A rename can no longer slip a matched image past the check: the worker reads the files under the same site lock the rename holds. A report the service accepted but whose status could not be saved is saved again, and the Report button refuses a second report because the evidence record already says it was filed. A restored site’s waiting checks run at once instead of up to an hour later. On Simple Hack, the uploader recorded for a team site’s deploy or files-storage upload is the team member (or organiser) who did it, not the event’s holding account, and the report names them. Reports and the admin list use only the uploader and address recorded at detection; an empty one stays empty. Re-uploading bytes whose check gave up queues the check again, and the admin queue line counts checks waiting for a deleted site (
site_deletedonGET /v1/admin/image-scan). Still off untilPHOTODNA_API_KEYis set. No migration. -
Nov 2: Simple Hack entries, slice 3: publishing and showing. The Website page now shows live whether your AI app is connected to your team and whether your site is published, with step-by-step tabs for Claude and ChatGPT, a ready-made prompt from your entry, and a page that updates by itself the moment Claude connects or publishes (new
GET /v1/hack/events/{slug}/site;hack_get_team_statusreports the same connection)./get-startedand the Website page read the same connect steps from one file. Published results now show what each team built: the summary card, with Open website, Watch video and View code, on the public page,/results,/publicand the AI apps, only for the rows the results setting shows (switching to full ranking needs no republish, and a site taken down later loses its link at once). Gallery cards show tool tags, and participant Results shows your entry as the public sees it. Teams whose entry isn’t submitted get a reminder email 24 hours and 1 hour before their deadline, naming what is missing; it respects the Account email switch and never goes to key-only accounts (migrationzx-hack-entry-reminders.sql). The privacy page names the new reminder. -
Nov 2: Image matching against known child sexual abuse material. Every image written to a site, to files storage, or as a Simple Hack event icon or entry screenshot is checked after the write against hash sets of known child sexual abuse material through Microsoft PhotoDNA Cloud Service. A Match check sends only the image bytes, never a name, email, or IP address. A Report, which the law requires after a match, sends the image, the account details of the uploader when known (the site owner for a site file, “anonymous visitor (no account)” for a files-storage upload by someone not signed in), the site address or event, both as recorded at detection, and the reporting organisation’s contact details to Microsoft’s PhotoDNA Report service, which files it with NCMEC’s CyberTipline. A match copies the original to an evidence folder, removes the matched bytes from every served copy (kept in place if the evidence copy fails), takes the site or event down, files the report automatically or from a Report button in the admin Moderation tab’s new Image matches section, and emails the operator a list of each step with done or FAILED. JPEG, PNG, GIF, and WebP are checked; BMP, TIFF, and images under 160 pixels on the short side are skipped. Failed checks retry from 1 minute, doubling to 6 hours, and give up after 12 tries (the admin page counts them; the last error is in the log and the queue table). A check for a site in Recently deleted waits and runs after a restore. The evidence folder for a match is always created fresh and never follows a symlink; if it already exists, the file is kept in place. It runs on server installs (systemd); Docker Compose small boxes do not pass the settings through yet. The whole feature is off until
PHOTODNA_API_KEY(orPHOTODNA_API_KEY_FILE) is set, and nothing is offered to users meanwhile, so this release changes nothing in production until the owner’s PhotoDNA application is approved; the runbook isdocs/image-matching.md. -
Nov 2: Simple Hack fixes from the full production test. Moving to Judging (or Closed) now settles every draft, so an Open-mode event with no deadline has its drafts judged, flagged Incomplete, and a team that only published its site is judged too; a team with no entry stays out. Overview’s Start judging confirm says how many teams will be judged and how many have no entry. Automatic assignment and Judging progress use the same teams as the judges’ queues, so a judge’s “0 of 2” matches what they see, and a judge with nothing to score reads “Nothing to score yet” instead of “you’ve scored everyone”. A date-only event end now lasts the whole day: the status bar reads “Ends · Wed 4 Nov” with no “12:00 am”, and Find a hackathon keeps the event under Happening now until that day is over. The reject dialog and the rejected applicant’s page now say what is true: the organiser can’t change a rejection, and the person can leave and apply again while the event takes applications. Home and Entry count the summary card the same way, and Entry lists what’s missing by field name. Results reads “1st of 2 judged teams” (and “Joint 1st” on a tie) using the new
ranked_teamson my-results. Security (review F1): a team site’s preview link is no longer given out when the site can’t be framed (passcode, named viewers, offline), and a judge only gets a team’s preview and deadline links for a team they may score, once that team can no longer change its site. Plus cosmetic fixes: tour card placement, Home headings, plural counts, alignment and spacing. No migration. -
Nov 2: Simple Hack entries, slice 2: the judge’s one screen. Scoring now opens on the team’s summary card, with the demo video and the team’s website on the same screen as the rubric, in the event’s order (video first, or website first for Coding). YouTube (played from youtube-nocookie.com), Vimeo, Loom and Google Drive videos play in place after the judge presses play, never before; the player address is rebuilt by the server from the parsed video id (
video.embed_urlon the judge queue and entries list), and any other link is a plain link naming its host. The website shows framed: the submitted (pinned) version, or a preview of the live one, from the server’ssite.preview_url, in a sandbox without top navigation. A site with a passcode or named viewers, offline, taken down or not ready is not framed (site.frameable: false,site.not_frameable_why) and shows the screenshot, the reason and Open website. Each criterion shows its weight, Save & next names any criterion left unscored once before moving on, N and P move between teams, and My teams shows each entry’s track and how far it works. Only the judge page’s Content-Security-Policy allows these frames (the four video players and the team-sites domain); every other page is unchanged, and team-site previews now allow the Simple Hack app to frame them. The MCP App judge view shows the same card, with the video and website as links. No migration. -
Nov 2: Simple Hack entries, slice 1: every entry now has a summary card (problem, a one-line solution, who it’s for, track, tools and AI, and what works today), and an explicit Submit. Organisers choose what a complete entry needs on Entries: a preset (AI build, Coding, Ideas and design) or Custom, with each line Required, Optional or Off, and the show-your-work lines also One of. Before saving tighter rules they see which teams it affects; tighter rules never un-submit an entry, and rules lock once entries close. Saving a draft never checks anything; Submit does, on the server, the same way on the website and in the AI apps (
hack_submit_entry,hack_unsubmit_entry,hack_set_entry_rules,hack_get_entry_rules,hack_set_entry_excluded). At a team’s deadline a complete draft is submitted automatically. An incomplete one is still judged, marked Incomplete, and organisers can exclude it by hand after a confirm. Home shows a four-step checklist and a countdown to the team’s own deadline. The entries CSV gains status, submitted time, the card fields, what’s missing and excluded. New routes:POST .../entry/submit,POST .../entry/unsubmit,GET/PUT .../entry-rules,POST .../teams/{team}/entry/excludeand/include;entry_requiredon the event is deprecated. Migrationzv-hack-entry-summary.sql(additive): existing events keep their old required list as Custom rules, and entries in events past Building count as submitted. -
Nov 2: Simple Hack: a schedule that acts. The event’s real times now show in its schedule by themselves as fixed rows that can’t drift: event start and end, the entry deadline (a participant sees their own team’s extension), the voting window and when results were published. Each says where it is set (“Set in Entries”) instead of having Edit. A schedule row can ask the organiser for the next step when its time comes, and the entry deadline always does: Overview then reads “Kickoff is now. Open sign-up?” or “Entries were due at 6:00 pm. Close entries?”. It only asks, the stage never moves by itself. Participants see “Demos starts in 12 minutes” and “Build time is on now” on their Home and Schedule, in the app only. API:
fixed_scheduleonGET/PUT /v1/hack/events/{slug}/contentand the public feed,schedule[].prompt,next_step.cue. MCP:hack_get_content,hack_set_content,hack_get_event. No migration. -
Nov 2: Simple Hack runs on Kubernetes from the one container image.
deploy/kubernetes/simple-hack/is a Helm chart (one pod,Recreate, a ReadWriteOnce volume at/data, a Secret with the generated admin key, passcode key and analytics salt kept across upgrades, a ConfigMap, a Service, an Ingress for<host>and*.<host>, an optional NetworkPolicy, probes on/healthzand/readyz, the restricted pod security standard with a read-only root filesystem, every value documented invalues.yaml),deploy/kubernetes/manifests/simple-hack.yamlis the same chart rendered to plain YAML (render.sh), anddocs/kubernetes.mdis the runbook (your Postgres and a role that owns the database, DNS for the apex and one wildcard, a TLS-terminating load balancer, the OIDC client, install, first sign-in, upgrades, backups, what doesn’t work without what). The binary learned two things for it:simple-host migrate -initbuilds an empty database from the embeddeddb/schema.sqlbefore applying migrations (no psql in the image; under the same advisory lock, so two pods starting at once build it once), and the server does the same before it listens whenMIGRATE_ON_START=true;TRUSTED_PROXY_CIDRSlists the networks the load balancer and ingress connect from, soX-Forwarded-Foris believed only from them and read right to left past every trusted hop (unset keeps the one-local-nginx rule). Team sites keep their own origin,https://<team>.<event>.<host>/: one DNS wildcard resolves both levels, and because an Ingress host wildcard and a wildcard certificate each cover one label, the chart adds a*.<event>.<host>rule for every slug underingress.eventsand the runbook asks for that SAN in the certificate (serving a team at<event>.<host>/<team>/was considered and not done: a shared origin would let one team’s page read another’s visitor sessions).deploy/kubernetes/test-chart.shchecks the chart without a cluster anddeploy/kubernetes/tests/kind-check.shinstalls it into a throwaway kind cluster with its own Postgres and uses the product (schema built on an empty database, an issued-key sign-in, an event, a joined participant, a published team site, the same after the pod is replaced; Playwright for the browser part). Thehack-v*release packages the chart (simple-hack-<chart>.tgzand inside the download) pinned to the release’s base image; no separate Kubernetes image is built. -
Nov 2: Simple Hack now tells people when something waits on them: a “Needs you” list on Team, Overview and Home covers pending join requests and invites, application answers, team site take-downs and restores, deadline changes and being made (or losing) team admin, plus the existing removal notice now shown on Team too.
hack_get_my_todosreads it across every event at once,hack_dismiss_noticesclears a news item, and a new Account switch, on by default, turns off the matching emails (hack_set_email_updates). Organisers only ever see application counts by email, never applicant names. Each kind emails at most once every 15 minutes, batched. -
Nov 2: Drafts as versions. An archive or files deploy (POST or PUT, with or without
?create=1) can now name who made the version with?author=(update_sitetakesauthorover the connector), andGET /v1/sites/{sitename}/versionsreturns it on every version;?pending=1lists only the versions stored withpublish=falsethat have never been live. A never-live version can be discarded for good withDELETE /v1/sites/{sitename}/versions/{version}(connector:discard_version; admin mirrorDELETE /v1/admin/sites/{id}/versions/{version}; its number is never reused): the live version answers 409version_live, one that has been live before answers 409version_published, and deploy-only and team keys are refused. The owner dashboard’s Versions list shows the author and a Discard button on drafts not live yet. Making a draft live is unchanged. A quotes console such as Simple Host for Travel can now keep one site per quote with its drafts as pending versions instead of a separatedraft-<name>site. Migrationdb/migrations/zw-sim-152-version-author.sql. -
Nov 2: Notifications now cover site events on Simple Host (agent notifications phase 2, SIM-356).
site.deployedfires when a version of a site goes live, through any deploy route or an active-version change (rollback, roll-forward, publishing a saved preview), with the version numbers and how it went live;domain.status_changedwhen a custom domain’s check records a status different from the previous one, or a long-failing domain is released, with the domain, both statuses, the check’s reason, and the certificate state;viewer.access_requestedwhen a person signed in with an email that is not on a named-viewers list reaches the no-access page, once per person per site per day; andvisitor.signed_upon a person’s first sign-in on a site. The last two carry the visitor ID only, never an email, and neither fires for the site’s owner. Same engine, same signatures, same receivers, and delivery history as the record events; a subscription’s storage filter still narrows record and file events only. Turn them on under Notifications on the dashboard, in theeventslist ofPOST /v1/sites/{sitename}/notifications, or over MCP withevents/listandevents/subscribe. Simple Host only for now: Simple Hack keeps the three record events and Enterprise has not ported the site events. Website skills 0.27.91. -
Nov 2: Your own visits no longer count as people. When you open one of your sites from a device you have used while signed in to Simple Host (the dashboard or the owner app), or after signing in on the site as yourself, those page views are filed as your own for 30 days and left out of People. You see them as a “You” figure on the site’s analytics page, every site in
GET /v1/sitesnow carriesviews(people in the last 7 and 30 days), and the connector states the figures in words inlist_sites,get_siteandsite_analytics. A visit from a device you never used while signed in still counts as a person, and other people behind the same address as a marked device are not counted while the mark lasts. A site you keep opening yourself still counts as in use for idle cleanup. Website skills 0.27.92. -
Nov 2: The public Features page (simple-host.app/features) is now a hierarchy explainer: what Simple Host is, a picture of its eleven areas, the features inside each one, and a detail view per feature (how it works, a real example, which editions have it, status, and where to read more), deep-linkable and readable without JavaScript. It renders from one data file,
internal/handler/static/features.json;make checknow fails when FEATURES.md gains a section or a bold-lead feature that file does not cover, or when the page is stale. -
Nov 2: Two Simple Hack audit fixes. Teams can now read the event’s rubric read-only (criteria, descriptions, weights, max points, never a score) from a “How you’re judged” card on the participant Entry screen, linked from Home;
GET /v1/hack/events/{slug}/rubricnow also accepts theparticipantrole, andhack_get_rubricworks the same way over MCP since it was always a thin passthrough. No organiser setting can hide it. In panel judging mode, a team with no track matches no panel and gets no judges; the organiser Judging screen’s Progress card and the Overview next-step card (before “Start judging”) now name every such team with a link to Teams, and the Start judging confirm repeats the count, computed client-side from data those screens already fetch. A third audit item, recording guardian consent for under-18 applicants, was dropped by owner decision (2026-11-02): events are for school and college students and organisers handle consent themselves.
October 2026
-
Oct 31: Simple Hack teams redesign: the creator of a team is now its admin. Admins now decide join requests and can lock or unlock the team. They can edit its name and looking-for note too, and remove a member. Admin status itself can change hands this way. A new team link can be rolled whenever needed. The last admin can’t be unmade until someone else is one, and the longest-standing remaining member succeeds an admin who leaves. “Who can join” is gone. Every unlocked team now takes a join request, and its link or code (
https://<hack host>/team/{code}, previewed before joining atGET /v1/hack/team-links/{code}) still joins instantly. A locked team clears its pending requests and invites and refuses every way in except organiser hand-placement. Team size now defaults to 20, and Fill teams asks for people per team (size, default 4) instead of filling to the event maximum. New routes:PATCH .../team,PUT .../team/lock,PUT .../team/members/{user_id}/admin,POST .../team/linkfor a team’s own admins, with organiser equivalents under.../teams/{team}/.... New MCP tools on both sides, andhack_set_team_findingis retired in favour ofhack_update_my_team. -
Oct 31: Simple Hack organiser Overview now shows one button instead of several. It performs the next forward move for the event’s stage, named by a new
next_stepfield on the organiser event view andhack_get_event. Moving the stage to Results now locks judging in the same step, closing the dead end where Results refused to publish an unlocked event. Participants and judges see the same stage pill and words as organisers, and the same stage track on their own home screen. Judges keep a separate scoring pill beside it. -
Oct 31: Simple Hack: an organiser MCP App (
ui://simple-hack/organiser), behindMCP_APP_HACK_ORGANISER(default off, same off/on/accounts: format). Overview and stage (next step, snapshot, Change stage with its confirm), People and approvals (applications with Approve/Reject, the new applicant fields, the member list), and the judging dashboard (rubric and assignment setup, progress, coverage, conflicts, lock/unlock, and deleting a departed judge’s scores), opened by the newhack_show_organisertool — gated the same way as the judge app, with each screen’s own flag checked independently so one flag being off never hides the other’s resource, listed and readable only once a connection has declared MCP Apps UI support, never for ChatGPT, OpenAI or Codex app names, and refused outright for anyone who isn’t an organiser of the event. Its own result carries only a fixed whitelist of event fields and aggregate counts, never the event’s join/judge codes or the organiser’s own display name, which travel to the view separately through_meta. Every plain organiser tool it reuses (hack_get_people,hack_decide_application,hack_get_judging_dashboard,hack_lock_judging, and 23 more) is unchanged, and an organiser-scoped wrapper around the host bridge refuses to call any other tool, capping concurrent calls at 4 and serialising writes. The view is the real website screens (organiser-overview.js,organiser-people.js,organiser-judging.js), reused unmodified apart from five documented patches for running inside a sandboxed frame instead of a page (two form-submission fixes and the Sign-up section’s own deep link, the same kind of fix the judge app’s invite form needed). Out-of-scope links (Teams, Entries, Results, Event page, Settings, the assignment grid — later phases) open the real website through the host’s own link confirmation instead of failing inside the frame. SIM-344 phase 2 (organiser core); the rest of the organiser surface and the participant app are later phases. -
Oct 31: Simple Hack paper metrics (SIM-335, deployed 2026-10-31; overhead-gate review): definition 4 replaces the unshipped five-minute/p99 design with one-minute start slots through judging, mergeable exponential histograms by class/status, in-flight and one-second arrival peaks, stable random event keys, synthetic flags, phase timelines and process provenance. Admin exports suppress people counts below five and normally omit events below five teams. Restart-safe baselines, panic cleanup and background stage refresh preserve accurate timelines; idle minutes write no rows, all event-key exports omit absolute dates/times and use decimal-string keys, derived judge/application counts are suppressed in daily and event rows, sparse pooled cells reduce slot memory, source-change keys deduplicate phase hooks across minutes, and off writes nothing. Activity expires after 400 days; Host collection and exports are unchanged.
-
Oct 31: Paper metrics for SIM-335: the server now keeps service-wide totals for the research papers (request time per kind of request, server CPU and memory every five minutes, a nightly count of sites, accounts and feature use, and a weekly anonymous size row per site), with an admin-only export at
GET /v1/admin/paper-metrics. Aggregates only, no IP or site name; the Privacy page says so.PAPER_METRICS=offturns it off. -
Oct 31: Simple Hack: a judge MCP App (
ui://simple-hack/judge), behindMCP_APP_HACK_JUDGE(default off, same off/on/accounts: format as the other Apps flags). Queue (“My teams”), scoring with tap-to-save point chips and “I know someone on this team”, the rubric with a Back control to return to the same team’s scoring, and accepting a judge invite, opened by the newhack_show_judgetool — listed and readable only once a connection has declared MCP Apps UI support, and never for ChatGPT, OpenAI or Codex app names, so the submitted ChatGPT app’s pinned tool list is unchanged; refused outright for anyone who isn’t a judge or organiser of the event, and its own result carries only a fixed whitelist of event fields, never an organiser’s join/judge codes. Every plain judge tool it reuses (hack_get_judge_queue,hack_score_team,hack_declare_my_conflict, and the rest) is unchanged, and a judge-scoped wrapper around the host bridge refuses to call any other tool. The view is the real website screens, reused unmodified apart from four documented patches for running inside a sandboxed frame instead of a page (accepting an invite and native form submission both needed fixes review caught live); two small website fixes (numeric coercion before interpolation, a host-name label next to external links) ride along. The nonce’d script-src CSP blocks an injected script even where escaping is missed, including an unescaped one injected directly into the live DOM. SIM-344 phases 0 (foundation) and 1 (judge); organiser and participant apps are later phases. -
Oct 31: Simple Hack: anyone can now leave an event, from Overview, Settings, a Home row menu, or
hack_preview_leave_event/hack_leave_event. A participant’s team is deleted if left empty, and leaving is blocked once that team’s deadline passes. A pending applicant can withdraw, and a rejected one can’t leave, so the decision stays on record. A judge’s scores stay and keep counting after they leave, and an organiser can delete them withhack_delete_former_judge_scores. The event’s creator hands it to another organiser first, and the only organiser must end or delete the event to leave it. -
Oct 31: Simple Hack: a person without a join link can now apply to an event from Find a hackathon or the event’s public page (
hack_preview_application,hack_apply_to_event). Applications are on by default and an organiser can turn them off per event in Settings. Every application waits for a decision in People → Applications, even when join-link sign-ups don’t. An applicant can optionally share a city, country, age range and gender, stored on the membership and never shown on public pages. -
Oct 31:
find_toolsnow names “adding or editing your own entry on a shared site” among the jobs it covers, and the visitor_read_site note that points to visitor_add_entry/visitor_change_entry now says to call run_tool with that name directly (or find_tools first). A Grok bot run of SIM-345 found Claude naming those tools itself after reading the note, then searching for them by that literal name instead of calling find_tools or run_tool, so cases 19 and 20 (adding and editing a visitor’s own board entry) always failed. -
Oct 30: The owner’s dashboard opens faster and no longer shows the public showcase first. “Your sites” now links straight to your own page once this browser knows your handle (skipping the /dashboard hop), the page hides the public gallery before it draws, and it asks the server for your account and your site list once each, in parallel, instead of five and three times. An admin’s own page now loads only their own sites rather than every account’s (632 KB for the hosted service). For 174 sites, My sites appears in about 0.3 s instead of about 1 s on a fast connection.
-
Oct 30: Simple Hack: the platform admin can join an event as an organiser (co-organiser invite) or with a join or judge code, like anyone else, and is then an ordinary member of that event with no admin bypass there; events it is not in stay read-only for it. In the Hack app, Sign out now sits in the sidebar foot (Account, Sign out, Help; on phone in the Menu sheet) instead of a one-button Session card on the Account page; Sign out everywhere stays in the Danger zone.
-
Oct 30: Connector passcode tools no longer return passcodes to the model or chat. The optional Passcode screen lets the person show, copy, set, or generate one using a sealed, single-use exchange. Other clients get a dashboard link that opens the existing Passcode dialog. The screen defaults off (
MCP_APP_PASSCODE); Hack has no passcode tools. Website skills 0.27.90. -
Oct 30:
visitor_read_sitejoins the compact tool listing (now 21 tools; OpenAI/ChatGPT flat listings unchanged at 58), after a connector-only Haiku 4.5 harness never called a tool at all in most runs of “someone shared a site with me” because no visitor tool was listed. Added a public Cost and limits page at /pricing stating this install’s own sites-per-account, storage, version and rate-limit numbers, generated from its configuration; linked from the footer and llms.txt. -
Oct 30: Fixes from the Grok bot’s tests. set_site_passcode can have the server pick the code (
generate: true), so the model never has to send a secret; removing a passcode that was never set now says nothing changed instead of “removed”. The connector instructions and the website-deploy skill tell Claude to publish a plain “make a website” request on Simple Host rather than only as an artifact (Sonnet 5 went from 0 of 3 to 3 of 3 on a plain business site in a claude.ai-style harness). Publishing a page with text after</html>(a find-and-replace that pasted the file into itself) now returns a fix-it warning. Website skills 0.27.89. -
Oct 30: visitor_read_site results name visitor_add_entry and visitor_change_entry in their note, so an agent that reads a shared sign-up sheet knows how to add the person’s entry.
-
Oct 30: When a connector call names a site that is not in the account, the error now points to visitor_read_site for a site shared with the person (Simple Host only). Found by a connector-only Claude Haiku 4.5 run that gave up on a shared sign-up page.
-
Oct 30: Sign-in review fixes: pages on the shared content host no longer get credentialed reads of other sites’ own hosts, even when an owner lists it; dashboard Sign out also ends this browser’s older sign-in family; hop starts and HEAD requests are checked as navigations before the rate limit; passcodes in run_tool string arguments and long numeric passcodes stay out of AgentCat.
-
Oct 30: Add the opt-in signed-in Hack app foundation, shared role shell, real Your events and Account screens, and the existing shared sign-in flow. Classic stays the default and remains reachable from Help and Account.
-
Oct 30: First-site sign-in asks everyone to Continue, including named viewers. Background sign-ins are blocked, pending handoffs leave no sign-in record, verified domain bindings are checked again at establishment, AI passcode limits are separate from browsers, and supplied secrets are removed from AgentCat text. Sign-in queries stay out of access logs.
-
Oct 29: Visitor tools omit account-bearing KV entries, redact account IDs in schema names, preserve large write values and IDs, and check site access before revealing resources. Website skills release 0.27.86.
-
Oct 29: Fixed visitor-tool discovery, privacy, pagination, exact numbers, page truncation, passcode exemptions, and owner visitor limits. Storage history stays separate from collection history, and connected apps show the last site used.
-
Oct 29: Added three connector tools for reading shared sites and adding or changing your own visitor entries, with fresh browser access checks, optional passcodes, a daily write cap, and app attribution in data history. OpenAI clients list 58 tools; the core list remains 20.
-
Oct 29: SSO sign-out links now require a matching browser family or confirmation, clear stored dashboard keys after pass expiry, refresh active pass idle expiry, fall back to legacy sign-in without an apex, and limit every public hop endpoint per IP.
-
Oct 29: SSO review fixes retire earlier browser sign-ins, complete site sign-out through the apex even after local expiry, preserve newer sign-ins in stale dashboard tabs, allow private-page sign-out redirects, bound pass issuance, and keep Sign in working when provider discovery fails. Website Deploy skills are version 0.27.85.
-
Oct 29: Site sign-in now hops through the account apex, remembers consent, and works on custom domains and Simple Hack. Signing out revokes the browser’s dashboard key and all site passes minted from it. Visitor-only accounts do not increase account growth or signup counts.
-
Oct 29: SIM-225 review fixes keep existing teams code-only, join crossed offers, check current finding settings, clean up removed people’s offers, respect extended deadlines during filling, and correct finding page state and team listing queries.
-
Oct 29: SIM-225 adds private team finding, join requests, solo listings and invites, teammate removal, and organiser team filling with a preview, on the website and through MCP.
-
Oct 29: The optional context input for AgentCat’s stated intent is now offered to every connector caller, ChatGPT, OpenAI, and Codex included, superseding the earlier exclusion pending plugin approval.
-
Oct 29: AgentCat receives tool-call arguments and results capped at 8 KB each, plus stated intent. The sender leaves out secrets, file contents, and raw visitor emails; AgentCat redacts personal identifiers before storage. Optional context is offered outside ChatGPT, OpenAI, and Codex pending plugin approval. Review fixes bound traversal, visit SQL cells once, omit rejected wrapper arguments, malformed edits and Hack contact emails, sanitize binary intent, and omit viewer-access error prose.
-
Oct 28: Restore Host SQL visitor reference parameters and Hack API-key own-conflict results, make Hack account email opt-in, preserve notification number precision, and key reviewer failure IP hashes with the connector process secret.
-
Oct 28: Matched the OpenAI submission to all 55 ChatGPT tools with MCP Events enabled, added a tool inventory and annotation consistency test, and rewrote the annotation justifications for current behavior.
-
Oct 28: Host connections from ChatGPT, OpenAI, and Codex list every permitted
-
Oct 28: Limit personal data in Hack MCP team, application, conflict, and judging results. Team roster emails require
include_emails: true, own conflicts stay scoped to the caller, and narrow mutations omit rosters and invitation codes. Preserve browser responses and tool schemas. Correct Hack tool annotations for overwrites, public effects, and deadline pinning. -
Oct 28: Host connector results omit unrequested account identity and viewer history, use site-scoped visitor references, and disclose emails only for explicit lookups. Download and preview links encrypt internal identifiers. Failed reviewer sign-ins log an IP hash. Existing tool names and output keys are unchanged.
-
Oct 28: Prepared the Simple Host 1.0.2 OpenAI resubmission with clearer hosting copy, less personal data in connector disclosures, revised skills, and matching reviewer tests.
-
Oct 28: Site listing scope and order.
GET /v1/sitesand MCPlist_sites -
Oct 27: MCP tuning from measured use.
create_upload_linkopens a photo -
Oct 28: The voting page shows the team name for your vote after a reload, says when one vote is removed, and no longer claims events are listed by default.
-
Oct 27: Event data includes scoring_open, so the judge page and the API agree on when scoring is open (including the standing demo while building). A screenshot change no longer causes a false “teammate changed this” warning.
-
Oct 27: Fixed entry conflict handling, scoring races, waiting-applicant admission, vote-removal confirmation, track removal and announcement editors. Website uploads reset cleanly, explain archive errors and respect the existing upload limit and team freeze before unpacking. Editing does not send a new email.
-
Oct 27: Error messages on simple-hack.app name support@simple-host.app instead of “whoever runs this server”.
-
Oct 27: Judging keeps scores when editing existing criteria and confirms score deletions, uses one entry order, refreshes generated assignments, skips conflicts, and includes organisers in automatic assignments only when requested. Judges see locks and wait until entries close to score. Public results link to team sites.
-
Oct 27: Simple Hack now explains sign-up errors and application status, asks what to do with waiting applicants when approval is switched off, confirms stage reversals, freezes extended entries at Judging, waits for publication before announcing results, removes votes that no longer qualify, starts new events outside the public directory, counts only existing events toward the daily limit, and returns empty results and notification lists for expected empty states.
-
Oct 27: Simple Hack now saves long track names, warns before removing chosen tracks or overwriting teammate entry text, serializes team saves, explains organiser removals, shows team tracks, reorders content, and edits or deletes announcements without resending email.
-
Oct 27: Team members and organisers can upload a website zip directly from Simple Hack, see the live address and version, and copy error details to get help fixing their files. Event websites also show recent versions and accept uploads in draft.
-
Oct 27: Small box on Railway.
deploy/platforms/railway/(a Dockerfile that copies the -
Oct 26: On the owner dashboard, a site’s Versions panel and its Storage/Rename/Domain panel no longer stack (SIM-211 follow-up): opening one closes the other, picking the same Manage item again closes it, Close returns focus to the Manage button, and opening a panel on a different site leaves the first site’s panel open. No change to what the panels do.
-
Oct 26: The dashboard’s Versions and Storage panels are easier to read: labels sit above their fields, each storage resource is its own card with one Save, adding storage sits behind an Add storage button, the tips fold under “What do these mean?”, the versions list shows the newest three and the live one with Show all, one sentence says how many versions are kept, and both panels have Close at the top. Same controls and requests as before.
-
Oct 26: Fixes from the ChatGPT free-account test. ChatGPT keeps a custom connector’s tool list from the day it was added, so it was still calling 2026-10-09 tool shapes: a call with an argument a tool no longer takes now gets the tool’s current arguments back and a line asking the person to refresh Simple Host in the app, and both Get started pages and llms.txt say to Refresh after updates. create_site and update_site now say a visitor form saves to storage through get_page_recipe (never mailto:) and point at create_upload_link’s photos link instead of asking for compressed photos; create_upload_link is offered whenever a page needs the person’s own photos. Two SQL statements in one call now say to run each as its own call.
-
Oct 26: The setup page’s existing-cluster path pins Enterprise chart 0.2.8 (release 0.9.10: site storage refusals say what happened and what to do, each with a stable
code; no schema change). -
Oct 26: SQLite storage errors now say exactly what went wrong and what to do, with a stable
sql_*code: a syntax error names the word, two statements, placeholder counts, PRAGMA and other unavailable features, the right route for a write or a schema change, a missing table or column (the owner sees the real names), and UNIQUE, NOT NULL, CHECK and foreign key failures naming the column. A wrong site name in the connector lists the account’s sites. -
Oct 24: WebMCP tools on the dashboard and Add photos page let a browsing agent (Gemini in Chrome, ChatGPT desktop) list sites, open one, change visibility, and add photos directly, with the same owner-only checks as the page itself; off entirely when nobody is signed in.
-
Oct 31: Small-box release v0.7.22 carries everything since v0.7.21: a faster owner dashboard (direct-to-sites routing, one parallel self/sites call instead of five and three), three connector tools for a shared site (
visitor_read_site,visitor_add_entry,visitor_change_entry) with fresh access checks, optional passcodes and a daily write cap, default-sites scoping and ordering with an admin-only?all=1/all_accountsswitch, MCP tool-set tuning from measured AgentCat use including batchedread_site_fileand in-placeupdate_siteedits, a Railway deploy recipe, SSO hop/sign-out and sign-in review fixes, WebMCP tools for browsing agents, SQLite storage errors with stable codes, and the Simple Host 1.0.2 OpenAI resubmission with less personal data in connector disclosures.zn-sso-hop.sql,zn-visitor-ai.sqlandzo-sso-signout-confirm.sqlrun on upgrade. Carries Simple Hack’s hack-v0.8.13 changes below in the same binary; the installer pins it. No DigitalOcean token was configured on the release host, so this was checked in local Docker containers instead of a droplet: a fresh v0.7.22 install (68 migrations,/healthz, the home page and/.well-known/mcp/server-card.jsonall answering 200) and a v0.7.21 box with a site and a KV value upgraded to v0.7.22 by a baremigratere-run, keeping both and applying the 7 new migrations once; the setup page and 1-Click, Coolify, Fly and Render pins use v0.7.22. The published image’s binary reportsv0.7.22 (commit 3a097ad). -
Oct 31: Simple Hack release hack-v0.8.13 carries everything since hack-v0.8.12: the new default Simple Hack web app (
static/hack, with?ui=classicfor the earlier screens), private team finding with join requests, invites, solo listing and organiser fill, announcement edit and delete, zip-upload and personal-data-minimisation fixes in Hack MCP, the organiser Event page split into sub-pages with a collapsible sidebar and walkthroughs, and applying to a hackathon without a join link from Find a hackathon or the event’s own public page (hack_preview_application/hack_apply_to_event, only for events listed in Find a hackathon, every application pending until an organiser decides, a newEVENT_APPLY_PENDING_PER_EVENTlimit).zk-hack-directory-opt-in.sql,zk-hack-team-removal-notice.sql,zl-hack-team-finding.sqlandzp-hack-applications.sqlrun on upgrade; the standalone package pins it. Checked the same way, in local Docker containers (no DigitalOcean token configured on the release host): a published hack-v0.8.12 install with an event, an admin-created participant, a team and a published team site, upgraded to hack-v0.8.13 with a baremigratere-run, keeping all of it and applying the 7 new migrations once; the standalone, Coolify and DigitalOcean pins use hack-v0.8.13. The published image’s binary reportsv0.8.13 (commit 3a097ad). Release checks. -
Oct 24: Small-box release v0.7.21 carries this and everything since v0.7.20 (a Go 1.27.3 toolchain with newer
golang.org/x/net(0.61.0) andx/image(0.47.0), clearing thecrypto/x509,crypto/tls,net/http, HTTP/2 and WebP advisories govulncheck reported against Go 1.27.1; no behavior change); the installer pins it. Verified on a real DigitalOcean droplet (sfo2,s-1vcpu-2gb): a v0.7.20 box with a site, a KV value and a records resource upgraded to v0.7.21 by a bare installer re-run, keeping its addresses, admin key and data (no new migrations); the setup page, 1-Click droplet, Coolify, Fly and Render pins use v0.7.21. The published image’s binary reportsgo1.27.3. -
Oct 24: Simple Hack release hack-v0.8.12 carries the same Go 1.27.3 toolchain and dependency bump as v0.7.21; the standalone package pins it. Verified on a real DigitalOcean droplet (sfo2,
s-1vcpu-2gb, a Let’s Encrypt certificate): a published hack-v0.8.11 install with an event, an admin-created participant, a team and a published team site upgraded to hack-v0.8.12 withupgrade.sh --image, keeping that data (no new migrations); the installer, Coolify and DigitalOcean pins use hack-v0.8.12. -
Oct 24: The setup page’s existing-cluster path pins Enterprise chart 0.2.7 (release 0.9.9: the photo picker, My sites, and the weekly dashboard MCP Apps default on, having passed Kubernetes smoke and MCPJam Apps conformance; a Go 1.27.3 toolchain and dependency bump clears webp and standard-library advisories). PARITY.md’s MCP Apps screens row is updated to match, identical in both repos.
-
Oct 24: Small-box release v0.7.20 carries this and everything since v0.7.19 (company sign-in through the operator’s own OpenID Connect provider and
EMAIL_SIGNIN=off, agent notifications with signing secrets sealed underPASSCODE_ENC_KEY, site search over generated summaries, the core MCP toolset’sfind_tools/run_tool, the photos page, MCP Apps behind off-by-default flags, JSON error envelopes for unsupported MCP methods, discovery documents and resource URNs,RateLimit-*headers,Idempotency-Key, and the Rounded icon); the installer pins it. Its migrations —zg-oidc-signin.sql,zh-site-notifications.sql,zi-site-search-summary.sqlandzj-hack-notifications.sql, plus the one-time site-summary backfill — run on upgrade. Verified on real DigitalOcean droplets (sfo2,s-1vcpu-2gb): a fresh install, and a v0.7.19 box with a site, a KV value and a records resource upgraded to v0.7.20 by a bare installer re-run, keeping its addresses, admin key and data, applying every new migration once, and generatingPASSCODE_ENC_KEY(then keeping it byte-for-byte on a second re-run); the setup page, 1-Click droplet, Coolify, Fly and Render pins use v0.7.20. -
Oct 24: Preserve and forward MCP Apps flags across small-box, Coolify, DigitalOcean, and standalone Hack installs, with all four off by default. Coolify generates and retains the sealing key and forwards company sign-in and notification limits. Add photo limits and Apps flags to the setup settings registry, derive preview frame origins from the instance hosts, and document the summary backfill after migration.
-
Oct 24: Add public Hack server and agent cards, landing Markdown, discovery headers, and Hack resource names and URNs on hosted and self-hosted instances. Keep the full Hack tool inventory and shorten personal instructions below 2,000 characters after hostname rewriting. Make auth.md describe configured Hack sign-in, company OIDC, connector OAuth, and selected teams; omit unavailable email steps on Host boxes. API error hints now link the instance’s own reference.
-
Oct 24: Add opt-in Simple Hack MCP Apps My sites and dashboard for selected teams and organiser event websites. Reuse existing authorised tools, keep entries as text, and forward the two default-off flags in the standalone package. Flags-off discovery and results are unchanged.
-
Oct 24: Simple Hack team and organiser websites now support MCP Events and signed webhooks, with sealed secrets, delivery controls, current membership checks, and creation deadlines. Apply
zj-hack-notifications.sqlbefore deploying. -
Oct 24: Simple Hack release hack-v0.8.11 carries this and everything since hack-v0.8.10 (Hack server and agent cards with discovery headers and resource URNs, opt-in MCP Apps My sites and dashboard, and MCP Events with signed webhooks); the standalone package pins it. Its migrations —
zh-site-notifications.sql,zi-site-search-summary.sqlandzj-hack-notifications.sql— run on upgrade. Verified on real DigitalOcean droplets (sfo2,s-1vcpu-2gb, Let’s Encrypt certificates): a fresh install (61 migrations), and a published hack-v0.8.10 install with an event, a team, a team key and a published team site upgraded to hack-v0.8.11, keeping that data and applying the three new migrations once; the installer, Coolify and DigitalOcean pins use hack-v0.8.11. -
Oct 24: Bound TIFF Deflate output in codec v3, check native photo dimensions before decoding, and give every decode path a deadline. The MCP picker checks worker and Wasm support before accepting HEIC/TIFF. Add photos checks uncertain saves against live bytes without creating duplicate versions.
-
Oct 24: Remove the attribution cookie and its 30-day cross-tab window; sign-ups keep validated same-visit URL/form labels, including OAuth and MCP consent. Bound each server’s Postgres pool (25 open, 5 idle, 30-minute lifetime, 5-minute idle timeout; configurable). Track the production unit with a 768M memory cap and add an uninstalled two-minute Signal uptime watch for both sites.
-
Oct 24: New Simple Host product icon, “Rounded”: a bold hand-drawn s.h monogram with a teal period, on a cream tile (reversed ink-tile colorway for light-page use). Replaces the dot-in-a-square mark everywhere Simple Host’s own icon appears: favicon.svg/.ico/32 px PNG, the 180 px apple-touch-icon, the host-toolkit logo downloads, the OpenAI plugin icon and logo, and the Simple Host Claude plugin icon. The icon cache-bust marker moves from
?v=bto?v=c. Simple Hack keeps its own red mark, unchanged. -
Oct 23: My sites always shows initial tiles instead of live thumbnails, with no nested frames or frame-domain exceptions in MCPJam. The site preview card remains off in production pending a framing decision or server-made preview images.
-
Oct 23: Owner product knowledge also reads the Chhota Break console and Simple Host for Travel plan from their own checkouts on this box, each labeled so answers never mix a live product with a plan.
-
Oct 23: Add four MCP Apps screens shown inside Claude, ChatGPT, and other MCP Apps hosts, each off by default behind its own flag (MCP_APP_PHOTO_PICKER, MCP_APP_MY_SITES, MCP_APP_DASHBOARD, MCP_APP_SITE_PREVIEW: off, on, or accounts:<handle>,…): a photo picker on create_upload_link that shrinks photos in the frame with the shared /photos code and saves them to images/ through update_site, My sites on list_sites with a weekly dashboard drill-in, and a site preview card on get_site with Open, Copy link, and Full screen. Frames call tools through the host bridge only and hold no key, cookie, or token; when the picker is on, photos_url is the sign-in /photos address without a token. Tool text and flags-off discovery are unchanged; the core toolset stays at 20.
-
Oct 23: Return a JSON-RPC error envelope for unsupported MCP HTTP methods (405) instead of the REST error body. MCPJam’s wire-schema check requires it for GET and DELETE probes.
-
Oct 23: Fix /.well-known/ard.json to the real ARD v0.91 shape (specVersion, host, entries with urn:air identifiers) and /.well-known/api-catalog to carry an RFC 9727 item array with the matching linkset+json profile content type. Link the MCP registry listing from docs.html. Add frontmatter (title, description, canonical) to the served homepage/index.md/llms.md and auth.md markdown, with canonical built from the instance’s own configured address rather than hardcoded.
-
Oct 23: Publish the MCP server to the official registry (registry.modelcontextprotocol.io) as app.simple-host/mcp, verified by a DNS TXT record on simple-host.app. mcp.so and Smithery listings need the owner’s own sign-in and are not done.
-
Oct 23: Cap the Idempotency-Key cache per account and in total, refusing new keys with 429 idempotency_cache_full once a cap is hit, so an authenticated caller cannot exhaust server memory with distinct keys (found in adversarial review of SIM-orank).
-
Oct 23: Restructure llms.txt with Markdown headings, use cases, and linked recipes and references, preserving operational details while reducing its size.
-
Oct 23: Add SoftwareApplication and Organization JSON-LD to the Simple Host landing and dashboard shell, retaining existing OpenGraph metadata.
-
Oct 23: Serve homepage markdown from its HTML copy through Accept negotiation, /index.md, and /llms.md; advertise the alternate and negotiate generic 404 bodies with Vary: Accept.
-
Oct 23: Add /.well-known/ard.json linking the MCP server, OAuth discovery, the existing skill index, and the REST API specification.
-
Oct 23: Serve the API catalog as application/linkset+json and add the YAML specification and HTML API reference links.
-
Oct 23: Advertise the sitemap, markdown alternate, API catalog, and OpenAPI description in both homepage formats’ HTTP Link headers.
-
Oct 23: Date compiled sitemap pages with embedded build time, with source revision time as the fallback for plain Go builds.
-
Oct 23: Add MCP server cards at /.well-known/mcp/server-card.json and /mcp/server-card, with the same version and endpoints as the agent card, and a small discovery index at /.well-known/ai-catalog.json.
-
Oct 23: Add GET /auth.md with OAuth and API-key sign-in documentation.
-
Oct 23: Report token-bucket capacity, remaining tokens and next-token delay in RateLimit headers, with accurate Retry-After on bucket refusals.
-
Oct 23: Accept Idempotency-Key on owner site create calls and resource/link creates, replaying the original response for 24 hours and rejecting a changed body with 409.
-
Oct 23: Raise OpenAPI JSON response-schema coverage from 60.4% to 87.4% with a reusable ErrorResponse and storage success schemas.
-
Oct 23: Return JSON with error codes and docs hints for unknown API and MCP routes and unsupported methods. Add missing codes to sign-in, throttling and oversized-upload errors while keeping visitor 404 pages as HTML.
-
Oct 23: mcp.simple-host.app now serves the MCP connector (was a dead address since the DNS-AID HTTPS record).
-
Oct 23: Give refused photo saves neutral error codes for 401, 403, 404 and 413, so photo-link holders cannot distinguish account-wide storage quotas from per-site caps.
-
Oct 23: Keep OAuth photo links valid for 60 minutes by rechecking the connection grant, even after the original access token expires. Disconnect, sign-out everywhere and account suspension still refuse the link. API-key expiry caps and archive links are unchanged.
-
Oct 23: Finish the Add photos round-2 fixes: time out stalled upload bodies, cap API-key photo-link lifetime at the key’s known expiry, remove fragment tokens from browser history, and keep Add more photos in the same page. Document ICC inspection limits and site-name binding.
-
Oct 23: Address the Add photos security review: bound concurrent saves before reading bodies, index collision checks, reject folder conflicts, cap ICC metadata, time out and bound worker decoders, preserve existing photo-named hosts, and send nosniff on small-box static files. Photo links share the same limits and return retry advice. Document the retained libde265 risk pending a patched prebuilt decoder.
-
Oct 23: Chat agents now give people a photo link that works without browser sign-in for one site, for an hour and up to 10 saves. Photos are shrunk on the device and added under images/ while keeping other files. create_upload_link defaults to this link; archive: true keeps the shell upload, and Simple Hack keeps its archive default.
-
Oct 23: Add a phone-friendly Add photos page and upload API. Photos are prepared on the device, saved together under images/ in one normal site version, and returned with copyable addresses. Existing files, quotas, and rollback are kept. Available on hosted and small-box Simple Host; Hack and Enterprise are not yet supported.
-
Oct 23: Publish a public DNS-AID capability document at
/.well-known/agent-card.jsonwith this server’s address, OAuth discovery links and current MCP tools. -
Oct 23: The connector lists 20 tools instead of 55: the building tools plus
find_tools, which finds the rest by the job in plain words, andrun_tool, which calls any of them by name with the same checks. Every tool still answers when called directly. Its instructions are now the cross-tool rules only, under 2,000 characters, and a signed-out tool error carries the reconnect steps. What an app loads before the person types drops from about 20,300 tokens to about 8,400. The skills, recipes, llms.txt and the MCPJam evals (new advanced-jobs suite) say how to reach the other tools. -
Oct 23: Privacy policy names AgentCat under “Who we share it with” and turns its MCP tool usage events on for hosted Simple Host.
-
Oct 23: Add optional minimal MCP tool usage events to AgentCat, off unless AGENTCAT_PROJECT_ID is set. The minimal payload is superseded by the 2026-10-29 context decision.
-
Oct 23: The API reference page has a short “Connect a domain” guide (four calls, the two DNS records, what to poll), and llms.txt points to it.
-
Oct 23: The MCP server answers
initializeandpingsent under the 2026-07-28 revision with method-not-found on HTTP 404, as that revision requires (older clients are unchanged), and repeats each tool’s title in its annotations for the connector directories. NewmcpjamCI workflow runs MCPJam protocol and OAuth conformance, host compatibility and the Claude directory policy against a local instance on every push and pull request, and an eval suite of the core jobs weekly. -
Oct 23: Find sites by description, date or page through REST and list_sites using compact summaries captured at deploy time, with a one-time backfill for existing sites.
-
Oct 23: Limit notification sealing to a bounded startup sweep, bind header tokens separately, keep unsubscribe working without the key, recover rotation after a key change, and replace installer configuration atomically.
-
Oct 23: Encrypt stored notification signing secrets and custom header tokens with the passcode key, and preserve that key on small-box installs.
-
Oct 22: Notification review fixes cap API-key subscription lifetimes, isolate OAuth subscription identities, redact MCP destination URLs, limit owner concurrency and URL delivery rates, exclude paused subscriptions from emission, and restrict callback addresses and custom headers.
-
Oct 22: Notification review fixes restrict deploy keys, preserve leases and retry budgets, queue emission after storage release, and correct callback verification, payloads, retention, and dashboard controls.
-
Oct 22: Simple Host phase 1 adds signed visitor-storage webhooks, MCP Events, and dashboard notification controls.