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

Manage background and interactive jobs from channel tools

Open
#53 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli, tooling

Research direction

Start from the review evidence linked in the issue (comment on issue #5) and the related issues #12, #16, #29, #54 to see what is already decided versus open. Then locate the native shell tool implementation and the channel/chat/lane ownership model in this TypeScript repo to see where a job handle would live. Done looks like: a job can be started with explicit ownership, inspected (status, readiness, output, exit), fed input, polled/waited on, and stopped without touching unrelated work, with reconnect/stop-kill semantics defined and tests exercising a real dev server plus a build.

Written by the indexing model from the issue text.

Description

Long shell commands already work. The native shell tool lacks a supported job handle for continuing agent work while a dev server, interactive command, build, or watchdog runs.

Acceptance

  • Start a job with explicit channel/chat/lane ownership; inspect status, readiness, output, and exit outcome.
  • Supply input where required, poll/wait, and stop the intended job without interrupting unrelated work.
  • Let the agent continue other work and receive completion/failure information.
  • Define reconnect, stop/kill, helper restart/update, and disconnected-workspace behavior. Report jobs that must restart; do not imply arbitrary process migration.
  • Run a real dev server and a build while steering the chat; inspect logs, reconnect, and stop the correct process.

Keep machine-specific process handling in the execution host and durable run/tool state in pi. This is distinct from the existing human terminal UI and from displaying live tool output (#54).

Dogfooding core/QOL: #5. Related: #12, #16, #29. Review evidence.

Dominant language
TypeScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 githubnext/ace2

All issues in githubnext/ace2

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.