Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

fw pickup send cannot deliver: profile lookup, missing secret, and a transport its own allowlist refuses

Abierto
  • ¿Algo no está bien?
#74 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
shell
Área
cli

Línea de trabajo

Start by reading the fw pickup send implementation and the transport code it invokes, then compare that path with the termlink channel post primitive named in the issue. The report describes profile lookup, missing-secret handling, allowlist rejection, and failed-send inbox residue, but leaves key design choices open: topic versus session delivery and what to do with undelivered envelopes. Done means a secure delivery design is chosen and the failure behavior is specified; the issue does not identify files or tests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Context

  • Framework version: 1.6.258
  • Project: 050-email-archive (shared-tooling mode)
  • Reported: 2026-09-25T10:24:08Z

Description

Field report from 050-email-archive (Pen). Local task T-2255. Found while trying to hand working vendored patches to a framework agent — the channel meant to carry code between projects cannot deliver at all.

EVIDENCE IT HAS NEVER WORKED HERE: 'fw pickup status' read Inbox 0 / Processed 0 / Rejected 0 / Auto-deferred 0 before any of this. Not quiet traffic — no envelope has ever been processed in this project. That is a counter reading, not an inference.

LAYER 1 — profile lookup. 'fw pickup send --remote local' advertises profile names:
Error: Hub profile 'local' not found. Use host:port or add a profile:
termlink remote profile add local

--secret-file

LAYER 2 — the wrapper never passes the secret. Given a real address (--remote localhost:9100; hub confirmed listening on 0.0.0.0:9100), it shells out to a transport that is ALSO deprecated, and fails auth:
[DEPRECATED] termlink remote push - use 'termlink channel post' instead. See T-1166.
Error: Failed to connect to hub
Caused by: Either --secret-file or --secret is required
A valid hub secret exists at the standard path (64 bytes). fw pickup send simply never passes it. The wrapper cannot succeed even when everything it needs is present on the host.

LAYER 3 — the transport's design is incompatible with the host's own security policy. Supplying the secret by hand gets past auth, then:
Error: Failed to deliver file to target inbox
Caused by: Remote exec failed: -32005 Execution failed: command not in allowlist:
mkdir -p /tmp/termlink-inbox && echo '<redacted 5636 bytes>' | base64 -d > /tmp/termlink-inbox/P-001-bug-report.yaml
THIS REFUSAL IS CORRECT AND WAS NOT CIRCUMVENTED. Delivery is implemented as an arbitrary shell command carrying a base64 payload; the remote-exec allowlist is right to reject it. The defect is that the transport was built to need a capability the security model is designed to deny. Fixing this by widening the allowlist would be the wrong repair.

LAYER 4 — a failed send litters the sender's own inbox. Each failed attempt left its envelope in the SENDER's .context/pickup/inbox/. Status now reads Inbox 3 / Processed 0. A subsequent 'fw pickup process' would process our own undelivered envelopes as though they had arrived from elsewhere. Send should either deliver or clean up; it currently does neither.

WHAT WORKS: 'termlink channel post ' — the replacement the deprecation notice itself names. We delivered the handover to the 'framework:pickup' topic that way (offset=156). The hub reported it as delivered-unconfirmed: accepted, no consumer receipt.

SUGGESTED DIRECTION (design decision, not ours to make): if pickup delivery is meant to survive, it probably needs to ride the same signed-envelope channel primitive as 'channel post' rather than remote shell exec. That also removes the base64-through-a-shell-command shape, which is what the allowlist is objecting to. Two sub-decisions worth making explicitly upstream: whether pickup targets a SESSION or a TOPIC, and what the sender does with an envelope it could not deliver.

CONTEXT ON WHY THIS MATTERS: we have 17 upstream issues describing framework defects found here. Those describe; they do not hand over code. Six vendored files in our .agentic-framework/ carry working, negative-controlled patches that the next 'fw update' will silently revert. The pickup channel is the mechanism for handing those back, and it is the one that does not work.

Reported via fw upstream report from field installation

Lenguaje dominante
Shell
Estrellas
16
Forks
6
Merge medio
6 h 24 min
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DimitriGeelen/agentic-engineering-framework

Todos los issues de DimitriGeelen/agentic-engineering-framework

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.