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

Foundation C: keep assistant handoff useful when setup is unavailable

Open
  • Is something wrong?
#281 4 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
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
accessibility, desktop, desktop-dev

Research direction

Start from HistorySelectionControls around the readiness block (baseline 7989426, lines 519–552), then HandoffJobs, SubscriptionCLI and existing delivery-feedback owners. Read docs/mac-foundation.md, the research note, spec PR #278, and issues #274/#275/#165 so host labeling and paste language are reused, not duplicated. Done means H1/H2 acceptance: copy/open/CLI stay distinct when assistants are unavailable, missing evidence is explained, identities and stale-callback races are preserved, with per-route evidence and no process-exit substitutes.

Written by the indexing model from the issue text.

Description

An optional assistant connection must not make prepared work unusable. Deliver package C of the focused Mac foundation under #7, completing existing HandoffJobs/manual-delivery owners.

Decided scope

  • Copy instructions stays first-class when inputs can be prepared safely. Text contains needed content/request; rich files expose exact attachments/folder steps. A path is not an attachment. Missing/unreadable evidence blocks with a reason, never silent omission.
  • Keep Copy instructions, Open receiving app and Run with a compatible CLI distinct. App launch is neither submitted nor running. Result available requires useful readable output linked to the exact task.
  • Project off/checking/missing executable/sign-in needed/unverifiable or restricted/input limit/incompatible/busy/ready/dispatch failure beside the selected destination. Retain manual delivery and the full review through setup and return; never auto-run.
  • Preserve immutable inputs, job/attempt identities and interruption receipts. An uncertain remote completion remains uncertain; explicit Retry cannot promise duplication-free execution.
  • Bind copied/opened/error feedback to attempt and resolved host. A stale first launch callback cannot overwrite a newer handoff notice; cover reversed completion of two attempts.

Starting points: HistorySelectionControls (readiness currently collapsed around lines 519–552 at baseline 7989426), HandoffJobs, SubscriptionCLI and delivery feedback. Consume #274 actual-host labeling and #275 research rather than duplicate them. Existing #165 manual paste work remains owned there; reuse its delivery language.

Boundaries

#63 separately owns Snap & Talk prompt/template/output contract and actual deck trial; no general rich-artifact runner, agent/MCP integration, credential migration, paid API substitute, organization-policy bypass or automatic cloud fallback. Do not create a universal permission framework. One existing receipt/result owner remains authoritative.

Acceptance

H1/H2: both assistants unavailable and text instructions still copied/pasted; actual attachment-only host roundtrip with exact selected files; setup return preserves review; meaningful missing-file/input-limit/unsupported-skill states; interruption, uncertain completion, explicit retry, exact result reuse and stale callback race. Each promoted connected runner/host route needs its own evidence. No process exit or window-open assertion substitutes for useful output.

Decision and evidence: spec PR #278, canonical brief, research. Baseline is main 7989426; reread current source/issues before implementation.

Implementation map: A #279; B #280; C #281; D existing #63; E existing #276; F #282; G #283; H #284. #7 remains the programme gate.

Adversarial sequencing: this useful output slice can ship independently through #7 with affected-path evidence. Do not wait for phone hardware, general Persona/Settings polish or new release automation. For further substantial investment, observe the complete useful result against the current alternative and later voluntary use.

Dominant language
Swift
Stars
0
Forks
1
Avg merge
8h 5m
Merged PRs (30d)
215

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 Ship-Work/workbench

All issues in Ship-Work/workbench

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.