feat: add top-level exec and shell commands by Hweinstock · Pull Request #52 · Hweinstock/agentcore-cli

Hweinstock · 2026-09-24T20:05:04Z

Summary

Add top-level agentcore exec with Runtime/Harness selectors and shared ARN resolution.
Add top-level agentcore shell while routing interactive flows through the existing Runtime shell and Harness exec screens.
Remove the nested harness exec and runtime shell command registrations.
Update command reference and user documentation.

Spec

Top-level exec and shell support Runtime/Harness resources under the hood and reuse the existing TUI flows. The requested resource resolver is implemented in src/handlers/utils.tsx.

Verification

bun run typecheck
bun run lint:check
bun run format:check
bun run compile
Focused handler and TUI tests: 154 passed
Full suite reached 3,447 passed; remaining failures were environment-restricted process/listener/network tests in the sandbox.

Account-backed Runtime/Harness execution and TUI recordings require account credentials and resource IDs, so those could not be captured in this environment.

Hweinstock · 2026-09-24T20:22:10Z

 import { JsonRendererKey } from "../tui";
+import type { Core } from "./types";
+
+export type ResourceType = "runtime" | "gateway" | "harness";


just inline this type, it doesn't deserve an alias?

Hweinstock · 2026-09-24T20:22:43Z

+}
+
+/**
+ * Given a resource type and identifier, resolve the resource's full ARN.


lets use tsdoc format here.

Hweinstock · 2026-09-24T20:27:10Z

      - [`agentcore traces runtime get`](#agentcore-traces-runtime-get)
    - [`agentcore traces harness`](#agentcore-traces-harness)
      - [`agentcore traces harness list`](#agentcore-traces-harness-list)
      - [`agentcore traces harness get`](#agentcore-traces-harness-get)


dont touch command.md manually.

Hweinstock · 2026-09-24T20:37:56Z

+  output: string;
+};
+
+export async function invokeExecCommand(


lets use a object here for the input args. ex. { core: Core, input: ExecInput, ...}

Hweinstock · 2026-09-24T20:40:47Z

+          await renderTuiAt(path, ctx, core, io);
+        } else {
+          const path = [
+            "/agentcore/runtime/shell",


We're going to want a single path: /agentcore/shell that supports both with a query param for resource type of something. The paths should match the underlying command structure.

Hweinstock · 2026-09-24T20:49:15Z

      "build",
    ],
  },
+  { id: "runtime", title: "Runtime commands", commands: ["exec", "shell"] },


why is this still here? I thought we removed runtime exec as a command?

Hweinstock · 2026-09-24T20:51:13Z

+        if (flags.command !== undefined || ctx.require(JsonKey)) {
+          throw new InputValidationError("specify one of --runtime or --harness");
+        }
+        await renderTuiAt("/agentcore", ctx, core, io);


im not sure why we would render the home page when running this command?

Hweinstock · 2026-09-24T20:52:17Z

+        if (flags["session-id"]) params.set("sessionId", flags["session-id"]);
+        if (flags.qualifier) params.set("qualifier", flags.qualifier);
+        await renderTuiAt(
+          `/agentcore/shell/${encodeURIComponent(resourceId)}?${params}`,


why is exec routing to shell?

Hweinstock · 2026-09-24T20:53:00Z

        path="agentcore/harness/exec/:harnessId/:sessionId"
        element={<HarnessExecScreen ctx={ctx} core={core} />}
      />
+      <Route path="agentcore/shell/:resourceId?" element={<ShellScreen ctx={ctx} core={core} />} />


i don't actually think we need a tui path for shell, shell just opens a shell. We would need one for exec.

Hweinstock · 2026-09-24T20:55:27Z

+export function HarnessExecScreen({
+  harnessId: routeHarnessId,
+  sessionId: routeSessionId,
+  routePath = "/agentcore/harness/exec",


lets simplify by removing exec under harness, and only supporting it at the top level.

Hweinstock · 2026-09-24T20:56:48Z

+export function RuntimeShellScreen({
+  runtimeId: routeRuntimeId,
+  qualifier: routeQualifier,
+  routePath = "/agentcore/runtime/shell",


same here, lets simplify by removing the nested ones.

Hweinstock · 2026-09-24T20:58:49Z

+import { RuntimeShellScreen } from "../runtime/shell/screen";
+import type { ScreenProps } from "../types";
+
+export function ShellScreen(props: ScreenProps) {


i don't think harness supports shell. also shell should not have a tui.

Hweinstock · 2026-09-24T20:59:21Z

 import { JsonRendererKey } from "../tui";
+import type { Core } from "./types";
+
+export type ResourceType = "runtime" | "gateway" | "harness";


inline this below on line 49.

Hweinstock · 2026-09-24T21:00:25Z

  - [`agentcore traces`](#agentcore-traces)
    - [`agentcore traces runtime`](#agentcore-traces-runtime)
      - [`agentcore traces runtime list`](#agentcore-traces-runtime-list)
      - [`agentcore traces runtime get`](#agentcore-traces-runtime-get)


undo diff to this one.

Hweinstock · 2026-09-24T21:09:47Z

      />
-      <Route path="agentcore/harness/exec" element={<HarnessExecScreen ctx={ctx} core={core} />} />
+      <Route path="agentcore/exec" element={<ExecScreen ctx={ctx} core={core} />} />
+      <Route path="agentcore/exec/:harnessId" element={<ExecScreen ctx={ctx} core={core} />} />


this needs to support runtime as well, so keep the harnessId general enough to resourceId. Then use the resourceType query parameter like we did before to determine the resource type.

Hweinstock · 2026-09-24T21:11:20Z

+
+      const resourceId = serviceIdFromArn(resourceArn);
+      if (flags.command === undefined) {
+        if (ctx.require(JsonKey)) {


i feel like we could simplify this here with an or to avoid the same error twice.

Hweinstock · 2026-09-24T21:11:37Z

+        return;
+      }
+
+      const result = await invokeExecCommand({


i want to be able to exec in runtime. see previous comment.

Hweinstock · 2026-09-24T21:11:57Z

-        breadcrumb={["agentcore", "harness", "exec"]}
+        breadcrumb={["agentcore", "exec"]}
        description="choose a harness to exec into"
-        onSelect={(id) => navigate(`/agentcore/harness/exec/${id}`)}


same comment on resource type.

Hweinstock · 2026-09-24T21:12:23Z

 import { JsonRendererKey } from "../tui";
+import type { Core } from "./types";
+
+export type ResourceType = "runtime" | "gateway" | "harness";


INLINE THIS

Hweinstock · 2026-09-24T21:19:47Z

-        path="agentcore/harness/exec/:harnessId/:sessionId"
-        element={<HarnessExecScreen ctx={ctx} core={core} />}
-      />
+      <Route path="agentcore/exec/:resourceId?" element={<ExecScreen ctx={ctx} core={core} />} />


lets just do agentcore/exec/:resourceType/:resourceId where resourceType is either runtime or harness.

Then we still need the agentcore/exec/:resourceType/:resourceId/:sessionId from below as well.

feat: add top-level exec and shell commands

8113ec3

Hweinstock force-pushed the feat/top-level-exec-shell branch from f2d3d12 to 8113ec3 Compare September 24, 2026 20:23

Hweinstock commented Sep 24, 2026

View reviewed changes

fix: address exec and shell review feedback

dc85a8e

Hweinstock commented Sep 24, 2026

View reviewed changes

fix: simplify exec and shell routing

e6bb43c

Hweinstock commented Sep 24, 2026

View reviewed changes

fix: support runtime exec routing

74c4ef7

Hweinstock commented Sep 24, 2026

View reviewed changes

Hweinstock added 4 commits September 24, 2026 21:21

fix: use explicit exec route parameters

9ecc9dc

fix: add dedicated runtime exec screen

f733fb2

fix: preserve resource exec and shell routes

01b8d2e

test: update resource command menus

5eb1928

Conversation

Hweinstock commented Sep 24, 2026

Summary

Spec

Verification

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant