Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

sessions: one place for sessions that need you (dropped, waiting at a prompt)

Open
#80 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
desktop

Research direction

The payload names no source files, so start by finding where the existing disconnect, reconnect and host-key/password/2FA prompt toasts are raised, and where the ⌘K picker and the status-line summary are built. The maintainers have not decided whether this is a separate panel or a section of the ⌘K picker, so a newcomer should first ask on the issue which option to build. Done means the chosen surface lists sessions in those states and selecting one switches to its tab.

Written by the indexing model from the issue text.

Description

area::tern kind::feature triage::needs-decision
What would you like to be added?

A short list of the sessions that need attention: disconnected, reconnecting, or waiting at a host-key, password or two-factor prompt. It opens from the status-line summary (see the status-line issue) or a shortcut, and picking an entry jumps to that tab.

Why is this needed?

These states only show up as toasts today, and a toast is easy to miss when you're in another tab. A host-key prompt even times out after 15 seconds. Shipyard's "Needs you" inbox for agents is the model.

Decision needed: whether this is its own panel, or part of the ⌘K picker (sessions that need you listed first).

Dominant language
Rust
Stars
2
Forks
2
Avg merge
1h 56m
Merged PRs (30d)
36

Getting set up

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 your-moon/tern

All issues in your-moon/tern

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.