Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug]: fw upgrade reinstalls the cross-host messaging toolkit (step 7b) on every run, with no way to opt out

Chiusa
  • Qualcosa non va?
#89 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
shell
Ambito
cli

Direzione di ricerca

Start with step 7b in lib/upgrade.sh (around lines 2536 and 2541), then check fw upgrade --help and lib/init.sh to understand the current behavior and the init/upgrade mismatch. The issue proposes several possible approaches, so clarify the opt-in or skip behavior before changing it. Done means projects that decline the toolkit do not have its files reinstalled on later upgrades, and the behavior is documented in the upgrade help or summary.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:upgrade bug severity:medium status:released triaged
Bug Description

Step 7b of fw upgrade, "Doorbell+mail toolkit (T-1867)", copies every file under lib/templates/skills/ and lib/templates/scripts/ into the project (lib/upgrade.sh, lines 2536 and 2541): nine slash commands in .claude/commands/ and twelve scripts in a new project-root scripts/ directory. There is no flag and no config key to skip the step, and fw upgrade --help lists none.

A project that removes these files gets them back on the next upgrade. T-3955 (479edae) made the step keep a file the project has customised; it does not cover a project that does not want the toolkit at all.

Why it matters: in a confidential workspace where nothing is meant to leave the machine and TermLink is not installed, a toolkit whose purpose is cross-host agent messaging is unwanted. It arrives without being announced as such, and has to be removed by hand after every upgrade.

Also: fw init does not install these files (no reference to the two template directories in lib/init.sh), so init and upgrade disagree on what a project contains.

Steps to Reproduce
  1. fw init a project. .claude/commands/ holds resume.md only, and there is no scripts/ directory.
  2. Run fw upgrade. Twenty-one files are created.
  3. Delete them, then run fw upgrade again.

Observed on 1.8.3 (with upstream at the same commit, so the upgrade brought nothing else) and again when upgrading to 1.8.6.

Expected Behavior

The messaging toolkit is installed only when the project asks for it, and a project that declined it is not asked again on each upgrade.

Actual Behavior

[7b/10] Doorbell+mail toolkit (T-1867)
CREATED .claude/commands/agent-handoff.md — from template
CREATED .claude/commands/be-reachable.md — from template
CREATED .claude/commands/broadcast-chat.md — from template
CREATED .claude/commands/check-arc.md — from template
CREATED .claude/commands/conversations.md — from template
CREATED .claude/commands/peers.md — from template
CREATED .claude/commands/pulse.md — from template
CREATED .claude/commands/recent-chat.md — from template
CREATED .claude/commands/recent-dm.md — from template
CREATED scripts/agent-chat-arc-recent.sh — from template
... (twelve scripts in all)

The same 21 files come back on every upgrade after being removed.

fw doctor output
AI Agent

Claude Code

Operating System

Linux

Additional Context

Version: 1.8.6 (1ea10441f), vendored consumer. First seen on 1.8.3.

Small inconsistency: fw upgrade --help announces "scripts/doorbell+mail supporting toolkit (11 .sh)"; twelve are installed.

Suggestions:

  1. Make the toolkit opt-in (config key or --with-messaging), or at least skippable, and remember the choice.
  2. Skip the step when TermLink is absent.
  3. Do not create a project-root scripts/ directory, which collides with a very common project folder name; keep the scripts under .agentic-framework/.
  4. Say in the upgrade summary that these files enable cross-host communication.
Lingua principale
Shell
Stelle
16
Fork
6
Merge medio
6h 24m
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DimitriGeelen/agentic-engineering-framework

Tutte le issue di DimitriGeelen/agentic-engineering-framework

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.