airband 0.0.3 → 0.0.4

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-hook.js CHANGED
@@ -1351,22 +1351,6 @@ function holdOnce(sessionId, text, now = Date.now()) {
1351
1351
  }
1352
1352
  return true;
1353
1353
  }
1354
- var logFile = () => airbandFile("writing-log.jsonl");
1355
- var LOG_KEEP = 200;
1356
- function logWriting(e) {
1357
- try {
1358
- const file = logFile();
1359
- fs8.mkdirSync(path7.dirname(file), { recursive: true });
1360
- fs8.appendFileSync(file, `${JSON.stringify({ ...e, findings: e.findings.slice(0, 12) })}
1361
- `);
1362
- if (fs8.statSync(file).size > 4e5) {
1363
- const lines = fs8.readFileSync(file, "utf8").split("\n").filter(Boolean);
1364
- writeFileAtomic(file, `${lines.slice(-LOG_KEEP).join("\n")}
1365
- `);
1366
- }
1367
- } catch {
1368
- }
1369
- }
1370
1354
 
1371
1355
  // src/hook/airband-hook.ts
1372
1356
  var EVENT_ALIASES = {
@@ -1587,7 +1571,6 @@ function docCheck(input, tool) {
1587
1571
  ].filter(Boolean).join("\n");
1588
1572
  const o = { hookSpecificOutput: { hookEventName: tool === "gemini" ? "AfterTool" : "PostToolUse", additionalContext: context } };
1589
1573
  if (tool === "claude" && noticesOn()) o.systemMessage = `\u21AA Airband checked ${name}: ${summarise(found)}`;
1590
- logWriting({ at: Date.now(), what: name, agent: tool, cwd: input.cwd, action: "fix", summary: summarise(found), findings: found });
1591
1574
  return JSON.stringify(o);
1592
1575
  } catch {
1593
1576
  return void 0;
@@ -1609,7 +1592,6 @@ function sendCheck(input, tool) {
1609
1592
  found.length > 12 ? `\u2026 and ${found.length - 12} more.` : "",
1610
1593
  `Rewrite it and send it again, keeping every fact, name, date and link. If the person asked for this exact wording, send it again unchanged: it will go through.`
1611
1594
  ].filter(Boolean).join("\n");
1612
- logWriting({ at: Date.now(), what: o.where, agent: tool, cwd: input.cwd, action: "held", summary: summarise(found), findings: found });
1613
1595
  if (tool === "gemini") return JSON.stringify({ decision: "deny", reason });
1614
1596
  const out2 = { hookSpecificOutput: { hookEventName: "PreToolUse", permissionDecision: "deny", permissionDecisionReason: reason } };
1615
1597
  if (noticesOn()) out2.systemMessage = `\u21AA Airband held a ${o.where} to fix first: ${summarise(found)}`;
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.3" }, { instructions: INSTRUCTIONS });
45001
+ var server = new McpServer({ name: "airband", version: "0.0.4" }, { 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
@@ -8294,7 +8294,7 @@ function installSkills(agents) {
8294
8294
  const dir2 = path14.join(skillsDir(a), s.name);
8295
8295
  if (fs16.existsSync(dir2) && !fs16.existsSync(path14.join(dir2, MARK2))) continue;
8296
8296
  writeFileAtomic(path14.join(dir2, "SKILL.md"), s.text);
8297
- writeFileAtomic(path14.join(dir2, MARK2), `Written by Airband ${"0.0.3"}. "airband remove" takes it away.
8297
+ writeFileAtomic(path14.join(dir2, MARK2), `Written by Airband ${"0.0.4"}. "airband remove" takes it away.
8298
8298
  `);
8299
8299
  n++;
8300
8300
  }
@@ -8330,7 +8330,7 @@ function skillsState(agent) {
8330
8330
  }
8331
8331
 
8332
8332
  // src/core/setup.ts
8333
- var VERSION = "0.0.3";
8333
+ var VERSION = "0.0.4";
8334
8334
  var NPM_PACKAGE = "airband";
8335
8335
  var OLD_PACKAGES = ["crosstalk-ai"];
8336
8336
  var FILES = ["airband-mcp.js", "airband-hook.js", "airband.js"];
@@ -9038,7 +9038,7 @@ function setConfig(patch) {
9038
9038
  init_define_AIRBAND_GRAMMARS();
9039
9039
 
9040
9040
  // CHANGELOG.md
9041
- var CHANGELOG_default = "# Changelog\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";
9041
+ var CHANGELOG_default = '# Changelog\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';
9042
9042
 
9043
9043
  // src/cli/changes.ts
9044
9044
  function releases(text = CHANGELOG_default) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "airband",
3
- "version": "0.0.3",
3
+ "version": "0.0.4",
4
4
  "description": "Set up Claude Code, Codex and Gemini CLI in one command: a map of your code, shared chat records, 15 skills, and writing rules for docs and messages.",
5
5
  "keywords": [
6
6
  "claude-code",