Recent-clients comment says Codex and Claude 'neither appears here any more' without qualifying gateway mode

Open Beginner friendly
#2,073 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
76/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
cli

Research direction

Read the comment at src/core/commands/status.js:809-811 and check how it describes Codex and Claude across capture modes. Qualify the claim so it is true in both modes; done when the comment no longer implies they never appear in recent-entrypoint rows.

Written by the indexing model from the issue text.

Description

Source: #2058 at 7d03bda413e08d5fe634258e90463768553d047a
Location: src/core/commands/status.js:809-811
Severity: trivial

Evidence

The comment states Codex left the gateway path in LLP 0429 and Claude in LLP 0262 'and neither appears here any more', which is unqualified and false for a codex configured with capture_mode: 'gateway', whose traffic still crosses the gateway and still produces recent-entrypoint rows.

Why deferral is safe

Comment prose only; no behavior. A one-clause qualification ('in their default modes') fixes it. Not worth a code round on this PR.

Acceptance condition

The comment qualifies the claim so it is true in both capture modes.

Review preference; backlog only. A human may explicitly delegate it with neutral:fix.

Dominant language
JavaScript
Stars
11
Forks
0
Avg merge
2h 55m
Merged PRs (30d)
294

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hyparam/hypaware

All issues in hyparam/hypaware

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.