The whole day,in one place.

1. 09:30Check-in at the desk.
2. 11:00Teams set. Rosters stay open after this: invite codes still work.
3. 12:00Idea saved. You can keep refining it after this.
4. 16:00–17:00Final evaluation at your team's table.
5. 18:00Submissions due.

curl -fsSL https://kaneclihack.sh/install.sh | sh

irm https://www.kaneclihack.sh/install.ps1 | iex

It installs the kanehack helper, the $hack-os and $hack-gtm skills, Kane CLI's release candidate (npm install -g @testmuai/kane-cli@rc) with the official kane-cli skill, and connects Codex to the event server, letting Codex's sandbox reach the network and ~/.kanehack. Say yes to each question.

$hack-os

When you've done something outside Codex (your terminal, your email, the browser), type done and it checks.

kanehack password

• New here: choose one (8+ characters). It is also your TestMu AI password.
• Registered on the site already: use that password.

• New here, or only checked in at the desk: kanehack register with your name, the email you registered for the event with, and LinkedIn (X and GitHub optional). It saves your profile and signs this machine in.
• Already registered: kanehack signin --email you@example.com.

• Start a team: team_create. Then the captain makes a join code with team_invite_create and gives one to each teammate.
• Join a team: give $hack-os the join code from your captain; it calls team_join.
• Go solo: a one-person team, also team_create.
• Looking for teammates: team_find, or https://kaneclihack.sh/match
• Lock it: when everyone is in, the captain runs team_lock. Nobody can join or leave after that (an organizer can reopen it).

• 01TestMu AI plan: kanehack claim. It uses your saved password and creates, or signs in to, your TestMu AI account.
• 02Password refused: the email already has a TestMu AI account with a different password. Save that account's password with kanehack password --testmu and claim again. Signed up there with Google or GitHub, or don't remember it? Set a new one at https://accounts.lambdatest.com/password/reset with the same email first.
• 03Codex coupon: codex_coupon_send emails it to the address you registered with, if you're on the participant list. Redeem it yourself, then tell $hack-os it's done.

• What it asks: your product name, app type, description and Kane CLI plan (which flows Kane tests, at least one assertion, and how your agent reacts to a Kane result).
• What you get: what to change, if anything, one question at a time.
• Saving it: idea_save, private to your team.

• Kane commands: the official kane-cli skill writes them. Kane CLI must be the release candidate: npm install -g @testmuai/kane-cli@rc.
• Recording runs: kanehack report -- kane-cli run "<objective>" --agent, after you agree to send a redacted summary (kanehack consent yes). Your team's runs so far: kanehack status.
• Kane's data, optional: read-only APIs (projects, explorations) to track your progress, show Kane's results in your app, or build a companion app.

• 01Say $hack-os ready to submit. It runs submission_preflight and lists what's missing.
• 02$hack-gtm drafts your launch posts, blog, a Show HN title and outline (you post it in your own words), deck and demo video. They're samples; you post them yourself.
• 03The Submit tab needs four things to finalize: project name, project description, a one-liner pitch and the GitHub repo URL (no commit SHA). Everything else is an optional link: showcase page, LinkedIn post(s), X post(s), blog link(s), deck, video and Hacker News post. Several posts go in one field, separated by commas. Your Codex session saves them and the captain finalizes there ($hack-os ready to submit); the Submit tab is the fallback.
• 04The shipped prize counts only from the Shipped prize bundle on your Submit tab, and preflight never checks it: the repo, a live URL or run command and a Kane CLI run report, plus any two of video, blog, X post and Show HN post. A signed-in teammate pastes each live link, ticks the row and presses Save, by 18:00 and before the captain finalizes.
• 05The demo video field takes a link. Put launch/video/showcase.mp4 on YouTube or Loom, or run kanehack publish launch/video/showcase.mp4 for a public link (it asks first; an agent adds --yes --json only after you say yes), and paste the link into Video and the bundle's Video row.
• 06The captain finalizes on the Submit tab, https://kaneclihack.sh/t/<team-slug>/submit.

• ENOTFOUND, UNREACHABLE or EPERM inside Codex: that's Codex's sandbox, not the event. Re-run the install command, say yes to connecting Codex, and start a new Codex session.
• "That password or code doesn't match this email": your account already has a different password. Save that one with kanehack password, then kanehack signin --email you@example.com. Forgot it? The help desk gives one-time codes.
• TestMu AI password refused: see step 06.
• A Kane command or flag isn't recognized: kane-cli --version, then npm install -g @testmuai/kane-cli@rc.
• Anything else: ask $hack-os for help (it starts with help_diagnose), or the help desk at https://kaneclihack.sh/help

• The skill: ~/.agents/skills/hack-os/SKILL.md after step 01. Read it and follow it.
• Event tools: the MCP server kane-hack-event at https://kaneclihack.sh/mcp, connected by the installer (the kanehack helper adds the sign-in header; no token is stored in the config). Without it: node ~/.agents/skills/hack-os/scripts/event-api.mjs call <tool> --args <file>.
• Every session: start with participant_get_status; it says where the person is.
• Rules: never ask for a password, key or coupon in chat. Anything public or hard to undo needs the person's yes to the exact content; they post and finalize submissions in the browser themselves. Never report something done unless the event server or a command said so.