Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Manage background and interactive jobs from channel tools

未關閉
#53 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
38/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
typescript
領域
cli, tooling

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
TypeScript
星號
1
分支
0
PR 合併指標
30 天內沒有已合併 PR

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

githubnext/ace2 的其他 Issue

查看 githubnext/ace2 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。