@ravshansbox/pi-next-issue 2.14.1 → 2.16.0

package/README.md

@@ -16,13 +16,13 @@ Run this in pi, inside a git repository:
 - The `next_issue_start` tool lets the model start a run. When no run is going, it starts a run like `/next-issue`. When a run is going, it starts nothing and reports the current run, which picks up new issues by itself. It never stops a run, and it does not ask for confirmation. Its result says whether it started a run.
 - The `next_issue_status` tool lets the model see the run of this repository. It returns the footer line, then one line per handled issue with its outcome, for example `#190 done`. When the worker has no run of this repository, it returns `next-issue · no run of <root>`. When no worker is going, it returns `next-issue · no worker is running` and does not start one. It reports no other repository.
 
-The footer shows the issue, the stage, the number of tool calls and the time spent on the issue, for example `next-issue #12 · review 1 · 37 tools · 4m12s`. After a run ends, it keeps the last summary. In the terminal, it uses the dim colour of the theme, like the rest of the footer. A note appears when an issue is done, needs a human or fails while pi is open. Pi does not repeat the notes of a run that ended before it opened.
+The footer shows each running issue with its stage, the number of tool calls and the time spent on it, for example `next-issue #12 · review 1 · 37 tools · 4m12s | #13 · implement · 5 tools · 40s`. After a run ends, it keeps the last summary. In the terminal, it uses the dim colour of the theme, like the rest of the footer. A note appears when an issue is done, needs a human or fails while pi is open. Pi does not repeat the notes of a run that ended before it opened.
 
 ## Answer questions
 
 When an issue waits for a person, with the `needsHuman` label of the [config](../next-issue/README.md), the footer shows the count, for example `2 questions waiting`, and a note appears once for each new question. Neither interrupts what you do. Pi asks the worker for the list when it connects and every minute, and the worker also sends it after each issue of a run. A question answered on GitHub or in another pi leaves the count with the next list.
 
-Run `/next-issue answer` to go through the waiting questions one at a time. Each shows the issue, the title and the reason of the hand-over. Choose:
+Run `/next-issue answer` to go through the waiting questions one at a time. Pi suggests `answer` as you type after `/next-issue `. Each shows the issue, the title and the reason of the hand-over. Choose:
 
 - **Retry**: takes the `needsHuman` label off the issue and its pull request, so the next run resumes it.
 - **Retry with guidance**: asks for text, posts it as a comment where the worker reads it, on the pull request of the issue or on the issue when it has none, then takes the `needsHuman` label off.

package/index.ts

@@ -68,20 +68,25 @@ function outcomes(progress: Progress): string {
 const OUTCOME_NOTES = { done: 'done', 'needs-human': 'needs a human', error: 'failed' } as const;
 
 export function formatStatus(progress: Progress, now: number): string {
+  const running = progress.issues ?? [];
   switch (progress.status) {
     case 'running': {
-      if (progress.issue === undefined) {
+      if (running.length === 0) {
         return 'next-issue · looking for issues';
       }
-      const parts = [`next-issue #${progress.issue}`, progress.stage ?? 'prepare'];
-      parts.push(`${progress.tools} tools`);
-      if (progress.issueStartedAt !== undefined) {
-        parts.push(duration(now - progress.issueStartedAt));
-      }
-      return parts.join(' · ');
+      const lines = running.map((item) => {
+        const parts = [`#${item.issue}`, item.stage ?? 'prepare', `${item.tools} tools`];
+        if (item.startedAt !== undefined) {
+          parts.push(duration(now - item.startedAt));
+        }
+        return parts.join(' · ');
+      });
+      return `next-issue ${lines.join(' | ')}`;
+    }
+    case 'stopping': {
+      const issues = running.map((item) => `#${item.issue}`);
+      return `next-issue ${issues.length === 0 ? '#?' : issues.join(' ')} · stopping`;
     }
-    case 'stopping':
-      return `next-issue #${progress.issue ?? '?'} · stopping`;
     case 'stopped':
       return `next-issue · stopped: ${outcomes(progress)}`;
     case 'finished':
@@ -440,6 +445,8 @@ export function createExtension(options: Options) {
     pi.registerCommand('next-issue', {
       description:
         'Start or stop working through the GitHub issues of this repository, or answer the waiting questions with "answer"',
+      getArgumentCompletions: (prefix) =>
+        'answer'.startsWith(prefix) ? [{ value: 'answer', label: 'answer' }] : null,
       handler: async (args, ctx) => {
         if (args.trim() === 'answer') {
           try {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ravshansbox/pi-next-issue",
-  "version": "2.14.1",
+  "version": "2.16.0",
   "description": "Pi extension that works through GitHub issues with the next-issue worker",
   "license": "MIT",
   "type": "module",

package/src/worker.ts

@@ -7,14 +7,18 @@ export type RunStatus = 'running' | 'stopping' | 'finished' | 'stopped' | 'faile
 
 export type Handled = { issue: number; outcome: 'done' | 'needs-human' | 'error' };
 
-export type Progress = {
-  status: RunStatus;
-  issue?: number;
+export type IssueProgress = {
+  issue: number;
   title?: string;
   stage?: string;
   tools: number;
   lastTool?: string;
-  issueStartedAt?: number;
+  startedAt?: number;
+};
+
+export type Progress = {
+  status: RunStatus;
+  issues: IssueProgress[];
   handled: Handled[];
   error?: string;
 };