Hack Day / Setup

Your agent,

Install one small helper, pair it with your passport, and connect Codex. Then Codex can do the day with you: team, idea, Kane runs, help and submission.

Step 01

Install the helper

Checks your machine, installs kanehack and the two hack-day skills ($hack-os and $hack-gtm), and makes kanehack a command. It asks before installing anything and never uses sudo.

  • macOS / Linux

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

  • Windows (PowerShell)

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

    Use the www address: Windows PowerShell 5.1 doesn't follow the redirect.

  • From an AI agent (no terminal)

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

    When Codex runs the installer it can't answer prompts; --yes answers them.

Step 02

Sign this machine in

Links kanehack to your passport so your runs and requests count for you and your team. Type your password in your own terminal, once; Codex never sees it.

  • In your own terminal, once

    kanehack password

    Your kaneclihack.sh password, typed hidden and kept in ~/.kanehack (mode 600). Never in a Codex chat.

  • Then (you or Codex)

    kanehack signin --email you@example.com

    New here? kanehack register --name "Your Name" --email you@example.com --linkedin <handle> [--x <handle>] saves your profile and signs in.

  • Or approve in the browser

    kanehack pair

    Approve the code it shows at /pair, signed in as yourself.

Step 03

Connect your agent

Points your agent at the event server, so the skills can read your status, record runs and open help tickets as you.

  • Codex

    kanehack connect codex

    The skills load from ~/.agents/skills (the installer puts them there). Start a new Codex session, then type $hack-os.

Step 04

Use the skill

Type $hack-os in Codex, or just ask in your own words. /skills lists it.

Get set up

  • hack-os

    Checks your machine, signs it in to your passport and connects Codex to the event, with the exact fix for anything missing.

    Try: “Show my Hack Day status and do my next step.”

Team and idea

  • hack-os

    Creates, joins or finds a team, then checks your idea against the challenge. Advisory, never a score.

    Try: “Find me a team that needs a frontend builder.”

Build and prove

  • hack-os

    Tests your project with Kane CLI and records runs on your team's Proof tab, failures included.

    Try: “Test our login flow with Kane and record it.”

Launch

  • hack-gtm

    Drafts your X and LinkedIn posts, blog, Show HN post, deck and a demo video with voice-over from your project and Kane evidence. Samples: you approve and post them yourself.

    Try: “Write our launch posts.”

Stuck

  • hack-os

    Tries first-line fixes, then drafts a GitHub issue on Kane CLI (you approve it) or opens a mentor ticket.

    Try: “I'm stuck: kane-cli run hangs.”

Kane CLI syntax comes from the official Kane CLI skill (npx @testmuai/kane-cli-skill). Publishing a Ship Page and taking your selfie stay with you in the browser; your agent hands you the link.

Step 05

Prove it works

Send one Kane run through kanehack. If it shows up on your team's Proof tab, you're set.

  • Your first reported run

    kanehack report -- kane-cli run "Open https://kaneclihack.sh and find the schedule" --agent

    It lands on your team's Proof tab.

  • Check your setup

    kanehack doctor

No terminal or agent? Everything works in the browser too: your passport and your team hub.