fleet: sandbox tailnet route to the laptop for the direct-API comms path (comms design G3) #2301

Activity

1. dezren39

   added

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   on Oct 29, 2026
2. developing-today commented on Oct 29, 2026

   

   developing-todayBot

   on Oct 29, 2026 – with developing.today

   Contributor

   More actions

   CODE-1155
3. dezren39

   added

   priority/normalOrdinary priority (the default)Ordinary priority (the default)

   on Oct 29, 2026
4. dezren39

   added a commit that references this issue on Oct 29, 2026

   docs(openclaw): link filed follow-ups #2300 #2301 #2302 in comms design

   e8ff494
5. github-actions

   assigned

   dezren39

   on Oct 29, 2026
6. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   source/creatorFiled by the new-issue-creator jobFiled by the new-issue-creator job

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 3, 2026
7. dezren39 commented on Nov 3, 2026

   

   dezren39

   on Nov 3, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done

   • Agent: queue worker (repo-worker-code), lane code-k
   • Session / ID: task 7888
   • Found via: queue claim
   • Task: Triage of issue fleet: sandbox tailnet route to the laptop for the direct-API comms path (comms design G3) #2301 (comms design gap G3) — verdict: the gap has closed since filing; the sandbox → laptop tailnet route is demonstrated. Closing issue fleet: sandbox tailnet route to the laptop for the direct-API comms path (comms design G3) #2301 with evidence.
   • Expectation: triage done = current-state verdict with fresh evidence.

   What changed since filing (verified fresh 2026-11-03):

   • At filing, the sandbox VM was not a tailnet node and its SSH CONNECT proxy refused proxied HTTP to the gateway. That premise no longer holds: the sandbox is now enrolled in the tailnet via Muse's Tailscale connector (this node: 100.115.16.3), with TCP egress to tailnet addresses through the runtime tunnel proxy.
   • The laptop (amd-6) is on the tailnet at 100.99.113.103 (confirmed from both sides: sandbox tailscale status and the laptop's own tailscale ip -4).
   • The OpenClaw gateway is listening on exactly the tailnet bind this issue targets: 100.99.113.103:18789 (openclaw-gateway.service active on the laptop).
   • Route demonstrated: from the sandbox, an HTTP request to http://100.99.113.103:18789/ through the tailnet tunnel returned HTTP 200 — the sandbox → laptop-gateway TCP path works at the network level, which is this issue's verification step (application auth remains the G2 follow-up's concern, as the issue itself scopes it).
   • Parent issue investigate: OpenClaw as a working option — setup state and a Muse↔OpenClaw comms path that is not laptop SSH #2023 is CLOSED (completed, 2026-10-30); the outcome is also recorded there per this issue's second acceptance criterion.

   Caveat for the record: the sandbox's tailnet presence is client-only via the connector tunnel (outbound TCP only, no inbound) — sufficient for the phase-2 direct-API comms path this gap blocked (Muse → gateway), which is the direction the design needed.
8. dezren39

   closed this as completedon Nov 3, 2026
9. dezren39

   removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 3, 2026
10. developing-today

    added

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    on Nov 3, 2026
11. developing-today commented on Nov 3, 2026

    

    developing-todayBot

    on Nov 3, 2026 – with developing.today

    Contributor

    More actions

    agent-note:v1
    state: triaged (coverage pass)
    Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
    Found via: coverage pass 2026-11-03