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

See what is running in the background: subagents and commands

Open
  • Is something wrong?
#89 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile

Research direction

Start by reading the session list and chat session UI, then trace how shell tool parts use shellID to follow output and how session.execution.started/ended events arrive for child sessions. The issue names the server endpoints to inspect: /api/session/active, /api/session?parentID=…, and /api/shell?location=…. Done means running subagents and commands can be inspected from the chat and session list, with shell output and stopping available as described; the attribution and terminal shell questions also need resolution.

Written by the indexing model from the issue text.

Description

feature
Problem

When the agent works in the background (subagents started with the task tool, shell commands that keep running), the app only shows that a session is running. There is no way to see what is running, neither inside the chat nor from the session list, nor to open or stop it.

Proposal
  1. In the chat: a "Running" indicator in the header (for example "2 subagents · 1 command") that opens a sheet listing everything running for this session:
    • subagents: title, agent, elapsed time, tap to open the child session;
    • background shell commands: command, elapsed time, last lines of output, Stop.
  2. In the session list: the row preview shows the same summary under the title while something runs (for example "Writing · 2 subagents · 1 command"), instead of only the running dot.
  3. Optionally, a global "Running" view from the session list, with everything running across sessions and projects of the active server.
Server API (2.0.27)
  • GET /api/session/active: sessions currently draining on the server.
  • GET /api/session?parentID=…: child sessions (subagents); session.execution.started/ended events already arrive for them.
  • GET /api/shell?location=…: running shell commands of a location (Shell.Info: command, cwd, pid, status, time, metadata); GET /api/shell/{id}/output for the output tail, DELETE /api/shell/{id} to stop.
Open questions
  • How to attribute a running shell to a session: the tool part metadata carries the shellID (already used to follow shell output live), but shells started elsewhere have no session.
  • Whether terminal (PTY) shells belong in the same list or stay separate (see #88).
  • Refresh: follow events where possible, and poll the shell list only while the sheet or the list is visible.
Dominant language
Kotlin
Stars
1
Forks
0
Avg merge
10h 37m
Merged PRs (30d)
42

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 beppe2880/opencode-mobile

All issues in beppe2880/opencode-mobile

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.