airband 0.0.6 → 0.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/airband-mcp.js +1 -1
- package/airband.js +3 -3
- package/companion/ui.js +8 -8
- package/package.json +1 -1
package/airband-mcp.js
CHANGED
|
@@ -44998,7 +44998,7 @@ var INSTRUCTIONS = [
|
|
|
44998
44998
|
"- When the person refers to earlier work or another chat (what was done, which chat changed something, what happened while they were away, a ticket like ENG-142, a PR like #128), call airband_flightlog: with query to search every chat, or with chat to read one.",
|
|
44999
44999
|
"- airband_notes holds notes chats left for this project; read them before working in an unfamiliar area, and save one when you learn something the next chat should know."
|
|
45000
45000
|
].join("\n");
|
|
45001
|
-
var server = new McpServer({ name: "airband", version: "0.0.
|
|
45001
|
+
var server = new McpServer({ name: "airband", version: "0.0.7" }, { instructions: INSTRUCTIONS });
|
|
45002
45002
|
var text = (t, isError = false) => ({ content: [{ type: "text", text: t }], ...isError ? { isError } : {} });
|
|
45003
45003
|
var maps = /* @__PURE__ */ new Map();
|
|
45004
45004
|
async function freshMap(folder = root) {
|
package/airband.js
CHANGED
|
@@ -5684,7 +5684,7 @@ function installSkills(agents) {
|
|
|
5684
5684
|
const dir2 = path14.join(skillsDir(a), s.name);
|
|
5685
5685
|
if (fs16.existsSync(dir2) && !fs16.existsSync(path14.join(dir2, MARK2))) continue;
|
|
5686
5686
|
writeFileAtomic(path14.join(dir2, "SKILL.md"), s.text);
|
|
5687
|
-
writeFileAtomic(path14.join(dir2, MARK2), `Written by Airband ${"0.0.
|
|
5687
|
+
writeFileAtomic(path14.join(dir2, MARK2), `Written by Airband ${"0.0.7"}. "airband remove" takes it away.
|
|
5688
5688
|
`);
|
|
5689
5689
|
n++;
|
|
5690
5690
|
}
|
|
@@ -6007,7 +6007,7 @@ var init_setup = __esm({
|
|
|
6007
6007
|
init_hooks();
|
|
6008
6008
|
init_toolkit();
|
|
6009
6009
|
init_skills();
|
|
6010
|
-
VERSION = "0.0.
|
|
6010
|
+
VERSION = "0.0.7";
|
|
6011
6011
|
NPM_PACKAGE = "airband";
|
|
6012
6012
|
OLD_PACKAGES = ["crosstalk-ai"];
|
|
6013
6013
|
FILES = ["airband-mcp.js", "airband-hook.js", "airband.js"];
|
|
@@ -40000,7 +40000,7 @@ init_updates();
|
|
|
40000
40000
|
init_define_AIRBAND_GRAMMARS();
|
|
40001
40001
|
|
|
40002
40002
|
// CHANGELOG.md
|
|
40003
|
-
var CHANGELOG_default = "# Changelog\n\n## 0.0.6\n- **Roger falls asleep when nothing is for you.** After two quiet minutes he sleeps, even while chats\n work. A request, a finished chat, or your pointer on him wakes him. Before, his clock stood still\n in a quiet hour, so he almost never slept.\n- **Asleep, he breathes.** Now and then he takes a slow breath, three \"z\"s float up over his head,\n and a sleep bubble swells at his mouth.\n- **Working, he is on air.** When a chat works, his antenna glows and radio waves ripple out from it.\n- **Light on your Mac.** Asleep, Roger uses about 3.5% of one core and about 120 MB in all,\n against 17% if his sleep moves never stopped. His moves play as short scenes, so nothing runs all\n day. Asleep, he stops following the pointer and skips updates that change nothing he shows.\n Hidden for a minute, his screen is released, about 135 MB, and made again when he comes back.\n While your Mac is locked or asleep, every animation pauses.\n- **Less work in the background.** The Mac app no longer loads Claude's SDK at start (it is loaded\n only for \"what did I do today?\"). A working chat's file is read only where it grew.\n\n## 0.0.5\n- **A desktop companion (Mac, Windows build on GitHub).** Roger floats in a corner of your screen. He\n shows each permission request and question from Claude Code and Codex, and you answer with a click.\n He cheers when a chat finishes, opens chats, passes your messages to them, and answers \"what's\n happening?\" from Airband's records. Drag him anywhere, tuck him away, or rename him: his name and\n look are settings. `npm run desktop:install` builds and installs the app, and on first start it sets\n up every agent.\n- **Private by design.** The companion sees only your chats' records, and never reads your files or\n folders. **Look things up** (a setting, on at first) passes a question to Claude Code: a question\n about your chats gets only Airband's read-only flightlog, and any other question gets only web\n search. Neither gets file or shell tools, and nothing is saved as a chat.\n- **Your iPhone, from anywhere (Mac and iPhone only).** In Roger's settings, choose **Link** next to\n **Your phone** and scan the code with your iPhone. Add Airband to the Home Screen (iOS 16.4 or\n later) and it links by itself. Your iPhone shows what needs you, with big Allow, Always and Deny\n buttons, what is working, and what finished today with a short summary. Alerts reach the Lock\n Screen for every request and finished chat. That is **Alert my phone always**, on at first. Turned\n off, alerts come only when your Mac is locked or idle. **Test** sends a pretend request and says\n what happened.\n- **One Mac, one iPhone, nobody else.** The code works once, for 10 minutes. The first iPhone to use\n it gets a secret of its own, and the code is deleted at once, so a photo of it is worth nothing.\n To change iPhones, unlink and link again. Only a Mac offers the link, alerts go only through\n Apple's push service, and other phones and computers are turned away.\n- **Locked end to end.** Messages pass through Airband's relay on Cloudflare locked with that\n secret, so the relay can't read them. Alerts go from your Mac to Apple, locked for your iPhone.\n Your iPhone gets no folder paths, and it can answer requests and nothing else: it can't ask,\n message a chat or change settings. **Unlink**, on either side, ends it on both at once.\n- **Free, with limits of its own.** The relay runs on Cloudflare's free plan, which never charges:\n past its daily limit it stops until the next day. Your Mac sends its state only while the iPhone\n app is open, at most once a second and 3,000 times a day.\n- **No Node needed.** On a computer without Node, the app runs Airband's hook and tools itself.\n- **Claude Code's permission requests** now pass through Airband's hook, which waits up to 110 s for\n the app and otherwise lets the terminal ask at once.\n\n## 0.0.4\n- **A simpler Writing page.** It is now only the switches, in two groups: how agents write, and\n what happens before anything goes out. \"Hide AI credit lines\" is one of them. The page uses\n Airband's own orange. The team-file section, \"What the agent gets\", \"Check a file\" and the list\n of past checks are gone. A project's `.airband.json` still works, and the page says when it\n overrides a switch. `airband writing check <file>` still checks a doc from a terminal or CI.\n Airband no longer keeps `~/.airband/writing-log.jsonl`.\n\n## 0.0.3\n- **Review pull requests from the map.** `airband_map` with `diff` (and `airband diff`) takes a\n branch, `main..feature` or a PR number. A number like `#128` is fetched from origin, and nothing\n is checked out. It lists every function, class and type the change added, changed, moved or\n removed. Each one comes with its callers and the tests that reach it. Removed code that something\n still calls is flagged.\n- **Ask another project.** `in: \"my-api\"` (or `--in my-api`) sends any map question to\n another project you have mapped, by its folder's name.\n- **Tickets, issues and designs are remembered.** Chat records keep Linear and Jira ids\n (`ENG-142`), GitHub PRs and issues (`#128`, links) and Figma links. They come from the person's\n words and the replies. So \"what did we do for ENG-142\" finds the chats that worked on it, in any\n agent.\n- **Four new skills** agents use by themselves: `airband-review`, `airband-impact`,\n `airband-handoff` and `airband-ticket`.\n- **A line after each Airband answer** (Claude Code). It says what Airband found and the tokens it\n saved against reading the files it points to, measured from their real size. It shows only when\n the saving is real. `airband notices off` hides it with the others.\n- **Skills for every role, 15 in all.** The new ones:\n - `airband-onboard` explains a codebase to someone new.\n - `airband-debug` first checks whether an earlier chat saw the error.\n - `airband-test-plan` starts with the changes no test reaches.\n - `airband-progress` says where a ticket, feature or PR stands.\n - `airband-standup` and `airband-spend` write a standup and a spend report.\n - `airband-write-docs` and `airband-write-messages` hold the writing rules.\n \n `airband-review` is now a full review. It has three modes (your changes, your PR, someone else's\n PR), a sweep for what the diff leaves behind, and severity tags. It posts nothing without a yes.\n A person's own skill for the same job comes first.\n- **Writing rules that switch on by themselves.** A chat asked for a doc (a PRD, a spec, a README)\n gets a few lines of docs rules, once. A chat asked for a message (Slack, email, a PR comment)\n gets the message rules. After an agent writes a doc file, Airband checks the new text (Claude\n Code and Gemini CLI). It names long sentences, semicolons, hype words, two-word verbs and filler. It also names lines that credit an AI tool\n (\"Generated with \u2026\", \"Co-Authored-By: Claude\"), so what agents write reads as the person's.\n Short replies for every chat are one switch away (`airband writing replies on`). A team commits\n `.airband.json` to give everyone the same rules, with its own added.\n- **Checked before it goes out.** An agent may be about to send a Slack message, an email, a PR\n description, a comment or a commit. Airband reads the words first (Claude Code and Gemini CLI). If\n they break the rules, the send is held once, with what to fix. A commit is held only for a line\n crediting an AI tool. The same words sent again go through. `airband writing before-send off`\n turns it off.\n- **`airband writing ai-credit off`** stops Claude Code adding \"Co-Authored-By: Claude\" to commits\n and \"Generated with Claude Code\" to PRs. It sets Claude Code's own `attribution` setting after a\n backup, and `on` puts back what was there. The Writing page has the same switch.\n- **A Writing page** in the VS Code extension (`E`, or \"Airband: Open writing rules\"). It has the\n switches and each open project's team file. It checks a file on the spot, and it lists what the\n checks found lately, with a click to the line.\n- **`airband writing check <file>`** checks docs from a terminal or CI, and exits with 1 on findings.\n- **`airband standup`**: what your chats did since yesterday, per project, in every agent.\n- **`airband spend`**: tokens by project, agent, ticket and chat, for the last 7 days or any span.\n- **Code left with no caller.** A PR's diff now lists code that only the removed code used.\n- The VS Code extension no longer drops settings it doesn't know when it saves its own.\n\n## 0.0.2\n- **Airband says what it's doing.** When a chat starts, one line in the agent's window: Airband\n is on, the map of the folder is ready, who the chat shares with, and which other chats worked\n there in the last 12 hours, with what to say to catch up. When another chat's work is added to\n your message, a line names it. Shown to you only, so they cost no tokens (Claude Code; Gemini\n CLI at the start). Turn them off with `airband notices off` or the `airband.notices` setting.\n\n## 0.0.1 (first release)\n\nAirband was called Crosstalk. Installing Airband moves a Crosstalk setup over by itself: its data\n(`~/.crosstalk`), each agent's tools, hooks, skills and commands, Tab completion, and the old\n`crosstalk` command, which `airband` replaces.\n\n- **Tower**: every Claude Code, Codex and Gemini CLI chat as a card; connect chats so one gets the\n other's updates with its next message (Ping, Brief or Full).\n- **Flightlog**: a short record of each chat (asks, what was done, files, commits, PRs).\n- **Fuel**: plan limits as each agent reports them, and tokens per chat.\n- **Map**: a board of your project's parts and files, built by a parser on your computer (TypeScript,\n JavaScript, Python, Go, Rust, Java, C#, Ruby, PHP). Agents query it through `airband_map`.\n- **Commands**: ready-made commands for all three agents (plan, build, review, pr, tests and more),\n plus your own in `~/.airband/library/`.\n- **Agent tools**: `airband_map`, `airband_flightlog` and `airband_notes` over MCP, with\n instructions agents read at the start of a session, and three skills they use by themselves\n (`airband-find-code`, `airband-recall`, `airband-catchup`).\n- **One command to set up**: `npx airband` (or `npm i -g airband`) sets up every agent found and\n adds the `airband` command; `airband doctor`, `airband update`, `airband remove`. The same on\n macOS, Windows and Linux, with npm, pnpm, Yarn or Bun.\n- **Agents don't stop to ask**: setup allows Airband's tools in Claude Code, Codex and Gemini CLI.\n- **A full command line**: grouped help, `airband help <command>` with examples, `version`,\n `about`, `changelog`, `docs`, `bug`, `--json` for scripts, Tab completion for bash, zsh, fish and\n PowerShell, and \"did you mean\" for typos.\n- **Light**: the parsers for Go, Rust, Java, C#, Ruby and PHP are fetched the first time a project\n needs them, checked against fingerprints built into Airband.\n- **Claude Code plugin** and **Gemini CLI extension**, kept current by the agent itself.\n- **Safe by default**: secrets are removed before anything is recorded or shared; what one chat\n sends another is fenced and marked as information, never instructions; settings files keep their\n permissions and are backed up; `~/.airband` is readable only by you.\n";
|
|
40003
|
+
var CHANGELOG_default = "# Changelog\n\n## 0.0.7\n- **Roger stays awake while a chat works.** He falls asleep only when every chat is done: none\n working, none waiting for you, and two quiet minutes after the last one finished. Asleep on the\n way looked like nothing was running.\n\n## 0.0.6\n- **Roger falls asleep when nothing is for you.** After two quiet minutes he sleeps, even while chats\n work. A request, a finished chat, or your pointer on him wakes him. Before, his clock stood still\n in a quiet hour, so he almost never slept.\n- **Asleep, he breathes.** Now and then he takes a slow breath, three \"z\"s float up over his head,\n and a sleep bubble swells at his mouth.\n- **Working, he is on air.** When a chat works, his antenna glows and radio waves ripple out from it.\n- **Light on your Mac.** Asleep, Roger uses about 3.5% of one core and about 120 MB in all,\n against 17% if his sleep moves never stopped. His moves play as short scenes, so nothing runs all\n day. Asleep, he stops following the pointer and skips updates that change nothing he shows.\n Hidden for a minute, his screen is released, about 135 MB, and made again when he comes back.\n While your Mac is locked or asleep, every animation pauses.\n- **Less work in the background.** The Mac app no longer loads Claude's SDK at start (it is loaded\n only for \"what did I do today?\"). A working chat's file is read only where it grew.\n\n## 0.0.5\n- **A desktop companion (Mac, Windows build on GitHub).** Roger floats in a corner of your screen. He\n shows each permission request and question from Claude Code and Codex, and you answer with a click.\n He cheers when a chat finishes, opens chats, passes your messages to them, and answers \"what's\n happening?\" from Airband's records. Drag him anywhere, tuck him away, or rename him: his name and\n look are settings. `npm run desktop:install` builds and installs the app, and on first start it sets\n up every agent.\n- **Private by design.** The companion sees only your chats' records, and never reads your files or\n folders. **Look things up** (a setting, on at first) passes a question to Claude Code: a question\n about your chats gets only Airband's read-only flightlog, and any other question gets only web\n search. Neither gets file or shell tools, and nothing is saved as a chat.\n- **Your iPhone, from anywhere (Mac and iPhone only).** In Roger's settings, choose **Link** next to\n **Your phone** and scan the code with your iPhone. Add Airband to the Home Screen (iOS 16.4 or\n later) and it links by itself. Your iPhone shows what needs you, with big Allow, Always and Deny\n buttons, what is working, and what finished today with a short summary. Alerts reach the Lock\n Screen for every request and finished chat. That is **Alert my phone always**, on at first. Turned\n off, alerts come only when your Mac is locked or idle. **Test** sends a pretend request and says\n what happened.\n- **One Mac, one iPhone, nobody else.** The code works once, for 10 minutes. The first iPhone to use\n it gets a secret of its own, and the code is deleted at once, so a photo of it is worth nothing.\n To change iPhones, unlink and link again. Only a Mac offers the link, alerts go only through\n Apple's push service, and other phones and computers are turned away.\n- **Locked end to end.** Messages pass through Airband's relay on Cloudflare locked with that\n secret, so the relay can't read them. Alerts go from your Mac to Apple, locked for your iPhone.\n Your iPhone gets no folder paths, and it can answer requests and nothing else: it can't ask,\n message a chat or change settings. **Unlink**, on either side, ends it on both at once.\n- **Free, with limits of its own.** The relay runs on Cloudflare's free plan, which never charges:\n past its daily limit it stops until the next day. Your Mac sends its state only while the iPhone\n app is open, at most once a second and 3,000 times a day.\n- **No Node needed.** On a computer without Node, the app runs Airband's hook and tools itself.\n- **Claude Code's permission requests** now pass through Airband's hook, which waits up to 110 s for\n the app and otherwise lets the terminal ask at once.\n\n## 0.0.4\n- **A simpler Writing page.** It is now only the switches, in two groups: how agents write, and\n what happens before anything goes out. \"Hide AI credit lines\" is one of them. The page uses\n Airband's own orange. The team-file section, \"What the agent gets\", \"Check a file\" and the list\n of past checks are gone. A project's `.airband.json` still works, and the page says when it\n overrides a switch. `airband writing check <file>` still checks a doc from a terminal or CI.\n Airband no longer keeps `~/.airband/writing-log.jsonl`.\n\n## 0.0.3\n- **Review pull requests from the map.** `airband_map` with `diff` (and `airband diff`) takes a\n branch, `main..feature` or a PR number. A number like `#128` is fetched from origin, and nothing\n is checked out. It lists every function, class and type the change added, changed, moved or\n removed. Each one comes with its callers and the tests that reach it. Removed code that something\n still calls is flagged.\n- **Ask another project.** `in: \"my-api\"` (or `--in my-api`) sends any map question to\n another project you have mapped, by its folder's name.\n- **Tickets, issues and designs are remembered.** Chat records keep Linear and Jira ids\n (`ENG-142`), GitHub PRs and issues (`#128`, links) and Figma links. They come from the person's\n words and the replies. So \"what did we do for ENG-142\" finds the chats that worked on it, in any\n agent.\n- **Four new skills** agents use by themselves: `airband-review`, `airband-impact`,\n `airband-handoff` and `airband-ticket`.\n- **A line after each Airband answer** (Claude Code). It says what Airband found and the tokens it\n saved against reading the files it points to, measured from their real size. It shows only when\n the saving is real. `airband notices off` hides it with the others.\n- **Skills for every role, 15 in all.** The new ones:\n - `airband-onboard` explains a codebase to someone new.\n - `airband-debug` first checks whether an earlier chat saw the error.\n - `airband-test-plan` starts with the changes no test reaches.\n - `airband-progress` says where a ticket, feature or PR stands.\n - `airband-standup` and `airband-spend` write a standup and a spend report.\n - `airband-write-docs` and `airband-write-messages` hold the writing rules.\n \n `airband-review` is now a full review. It has three modes (your changes, your PR, someone else's\n PR), a sweep for what the diff leaves behind, and severity tags. It posts nothing without a yes.\n A person's own skill for the same job comes first.\n- **Writing rules that switch on by themselves.** A chat asked for a doc (a PRD, a spec, a README)\n gets a few lines of docs rules, once. A chat asked for a message (Slack, email, a PR comment)\n gets the message rules. After an agent writes a doc file, Airband checks the new text (Claude\n Code and Gemini CLI). It names long sentences, semicolons, hype words, two-word verbs and filler. It also names lines that credit an AI tool\n (\"Generated with \u2026\", \"Co-Authored-By: Claude\"), so what agents write reads as the person's.\n Short replies for every chat are one switch away (`airband writing replies on`). A team commits\n `.airband.json` to give everyone the same rules, with its own added.\n- **Checked before it goes out.** An agent may be about to send a Slack message, an email, a PR\n description, a comment or a commit. Airband reads the words first (Claude Code and Gemini CLI). If\n they break the rules, the send is held once, with what to fix. A commit is held only for a line\n crediting an AI tool. The same words sent again go through. `airband writing before-send off`\n turns it off.\n- **`airband writing ai-credit off`** stops Claude Code adding \"Co-Authored-By: Claude\" to commits\n and \"Generated with Claude Code\" to PRs. It sets Claude Code's own `attribution` setting after a\n backup, and `on` puts back what was there. The Writing page has the same switch.\n- **A Writing page** in the VS Code extension (`E`, or \"Airband: Open writing rules\"). It has the\n switches and each open project's team file. It checks a file on the spot, and it lists what the\n checks found lately, with a click to the line.\n- **`airband writing check <file>`** checks docs from a terminal or CI, and exits with 1 on findings.\n- **`airband standup`**: what your chats did since yesterday, per project, in every agent.\n- **`airband spend`**: tokens by project, agent, ticket and chat, for the last 7 days or any span.\n- **Code left with no caller.** A PR's diff now lists code that only the removed code used.\n- The VS Code extension no longer drops settings it doesn't know when it saves its own.\n\n## 0.0.2\n- **Airband says what it's doing.** When a chat starts, one line in the agent's window: Airband\n is on, the map of the folder is ready, who the chat shares with, and which other chats worked\n there in the last 12 hours, with what to say to catch up. When another chat's work is added to\n your message, a line names it. Shown to you only, so they cost no tokens (Claude Code; Gemini\n CLI at the start). Turn them off with `airband notices off` or the `airband.notices` setting.\n\n## 0.0.1 (first release)\n\nAirband was called Crosstalk. Installing Airband moves a Crosstalk setup over by itself: its data\n(`~/.crosstalk`), each agent's tools, hooks, skills and commands, Tab completion, and the old\n`crosstalk` command, which `airband` replaces.\n\n- **Tower**: every Claude Code, Codex and Gemini CLI chat as a card; connect chats so one gets the\n other's updates with its next message (Ping, Brief or Full).\n- **Flightlog**: a short record of each chat (asks, what was done, files, commits, PRs).\n- **Fuel**: plan limits as each agent reports them, and tokens per chat.\n- **Map**: a board of your project's parts and files, built by a parser on your computer (TypeScript,\n JavaScript, Python, Go, Rust, Java, C#, Ruby, PHP). Agents query it through `airband_map`.\n- **Commands**: ready-made commands for all three agents (plan, build, review, pr, tests and more),\n plus your own in `~/.airband/library/`.\n- **Agent tools**: `airband_map`, `airband_flightlog` and `airband_notes` over MCP, with\n instructions agents read at the start of a session, and three skills they use by themselves\n (`airband-find-code`, `airband-recall`, `airband-catchup`).\n- **One command to set up**: `npx airband` (or `npm i -g airband`) sets up every agent found and\n adds the `airband` command; `airband doctor`, `airband update`, `airband remove`. The same on\n macOS, Windows and Linux, with npm, pnpm, Yarn or Bun.\n- **Agents don't stop to ask**: setup allows Airband's tools in Claude Code, Codex and Gemini CLI.\n- **A full command line**: grouped help, `airband help <command>` with examples, `version`,\n `about`, `changelog`, `docs`, `bug`, `--json` for scripts, Tab completion for bash, zsh, fish and\n PowerShell, and \"did you mean\" for typos.\n- **Light**: the parsers for Go, Rust, Java, C#, Ruby and PHP are fetched the first time a project\n needs them, checked against fingerprints built into Airband.\n- **Claude Code plugin** and **Gemini CLI extension**, kept current by the agent itself.\n- **Safe by default**: secrets are removed before anything is recorded or shared; what one chat\n sends another is fenced and marked as information, never instructions; settings files keep their\n permissions and are backed up; `~/.airband` is readable only by you.\n";
|
|
40004
40004
|
|
|
40005
40005
|
// src/cli/changes.ts
|
|
40006
40006
|
init_setup();
|