feat(runtime): add Runtime invocation

README.md

@@ -58,6 +58,7 @@ agentcore                          # interactive TUI
 ├── runtime                        # inspect deployed AgentCore Runtimes
 │   ├── get                        # fetch a Runtime by id
 │   ├── list                       # list Runtimes (server-side paginated)
+│   ├── invoke                     # invoke a Runtime headlessly or in a persistent console
 │   ├── version
 │   │   ├── get                    # get a specific Runtime version
 │   │   └── list                   # list a Runtime's versions
@@ -116,6 +117,91 @@ agentcore identity api-key-credential-provider update --name my-provider --api-k
 agentcore identity api-key-credential-provider delete --name my-provider
 ```
 
+### Invoke a Runtime
+
+Headless invocation accepts inline, file, or stdin payload bytes:
+
+```bash
+# Inline
+agentcore runtime invoke \
+  --id <runtimeId> \
+  --payload '{"action":"status"}' \
+  --content-type application/json \
+  --accept text/event-stream
+
+# File
+agentcore runtime invoke --id <runtimeId> --payload file://request.json
+
+# stdin
+cat request.json | agentcore runtime invoke --id <runtimeId> --payload -
+```
+
+CUSTOM_JWT Runtimes require `--bearer-token`. The token accepts the same inline,
+`file://`, or stdin sources as the payload; payload and token cannot both read
+stdin.
+
+```bash
+agentcore runtime invoke \
+  --id <runtimeId> \
+  --payload file://request.json \
+  --bearer-token file://$HOME/.config/agentcore/runtime-token
+```
+
+For MCP Runtimes, initialize first, then pass the returned Runtime and MCP
+session IDs to later methods. MCP requests accept both JSON and SSE responses.
+
+```bash
+agentcore runtime invoke \
+  --id <runtimeId> \
+  --payload '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"agentcore-cli","version":"1"}}}' \
+  --accept 'application/json, text/event-stream' \
+  --mcp-protocol-version 2025-03-26 \
+  --mcp-method initialize
+
+agentcore runtime invoke \
+  --id <runtimeId> \
+  --payload '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \
+  --accept 'application/json, text/event-stream' \
+  --session-id <returnedRuntimeSessionId> \
+  --mcp-session-id <returnedMcpSessionId> \
+  --mcp-protocol-version 2025-03-26 \
+  --mcp-method tools/list
+```
+
+Raw mode streams exact response bytes to stdout and writes response metadata to
+stderr. Use `--output-file` for binary responses. `--json` instead buffers one
+response and emits a metadata envelope without interpreting the customer body.
+
+```bash
+agentcore runtime invoke \
+  --id <runtimeId> \
+  --payload file://request.bin \
+  --content-type application/octet-stream \
+  --accept application/octet-stream \
+  --output-file response.bin
+
+agentcore runtime invoke --id <runtimeId> --payload '{"action":"status"}' --json
+# {"statusCode":200,"contentType":"application/json","bodyEncoding":"utf8","body":"{\"ok\":true}","complete":true}
+```
+
+Without `--payload`, Runtime Invoke opens a persistent console for repeated
+requests. Bare invoke opens the Runtime and endpoint pickers; `--id` skips the
+Runtime picker, and `--id` plus `--qualifier` opens the console directly.
+
+| Shortcut | Action                                       |
+| -------- | -------------------------------------------- |
+| `Ctrl+D` | Send the request                             |
+| `Ctrl+O` | Open Request Options                         |
+| `Ctrl+T` | Change Runtime or endpoint                   |
+| `Ctrl+V` | Toggle raw and pretty completed JSON         |
+| `Esc`    | Interrupt an active request or navigate back |
+| `↑`/`↓`  | Scroll response history                      |
+
+Runtime Invoke accepts Runtime IDs from the current account only. It does not
+accept ARNs, `--version`, `--interactive`, cross-account targets, or custom
+request paths. All requests use the Runtime `/invocations` route, including MCP
+Runtimes.
+
 Bare Runtime branches and leaves require a TTY on stdin and stdout. Supplying
 operation flags runs the command headlessly, and `--json` always suppresses TUI
 rendering.

package.json

@@ -49,7 +49,7 @@
     "typescript": "^5"
   },
   "dependencies": {
-    "@aws-sdk/client-bedrock-agentcore": "^3.1079.0",
+    "@aws-sdk/client-bedrock-agentcore": "^3.1092.0",
     "@aws-sdk/client-bedrock-agentcore-control": "^3.1079.0",
     "@aws-sdk/client-iam": "^3.1080.0",
     "@inkui-cli/data-table": "^0.2.0",

src/components/Root.tsx

@@ -28,6 +28,7 @@ import { RuntimeListEndpointsScreen } from "../handlers/runtime/endpoint/list/sc
 import { RuntimeVersionScreen } from "../handlers/runtime/version/screen.tsx";
 import { RuntimeGetVersionScreen } from "../handlers/runtime/version/get/screen.tsx";
 import { RuntimeListVersionsScreen } from "../handlers/runtime/version/list/screen.tsx";
+import { RuntimeInvokeScreen } from "../handlers/runtime/invoke/screen.tsx";
 import { RootScreen, HelpScreen } from "../handlers/screen.tsx";
 import type { Context } from "../router";
 
@@ -255,6 +256,18 @@ export function Root({ path, ctx, core, queryClient }: RootProps) {
             path="agentcore/runtime/endpoint/list/:runtimeId"
             element={<RuntimeListEndpointsScreen ctx={ctx} core={core} />}
           />
+          <Route
+            path="agentcore/runtime/invoke"
+            element={<RuntimeInvokeScreen ctx={ctx} core={core} />}
+          />
+          <Route
+            path="agentcore/runtime/invoke/:runtimeId"
+            element={<RuntimeInvokeScreen ctx={ctx} core={core} />}
+          />
+          <Route
+            path="agentcore/runtime/invoke/:runtimeId/:qualifier"
+            element={<RuntimeInvokeScreen ctx={ctx} core={core} />}
+          />
           <Route path="*" element={<HelpScreen ctx={ctx} core={core} />} />
         </Routes>
       </MemoryRouter>

src/components/RuntimeEndpointPicker.tsx

@@ -27,6 +27,7 @@ export interface RuntimeEndpointPickerProps extends ScreenProps {
   breadcrumb: string[];
   description?: string;
   onSelect: (qualifier: string) => void;
+  onEscape?: () => void;
 }
 
 export function RuntimeEndpointPicker({
@@ -36,10 +37,11 @@ export function RuntimeEndpointPicker({
   breadcrumb,
   description,
   onSelect,
+  onEscape,
 }: RuntimeEndpointPickerProps) {
   const opts = coreOptsFromCtx(ctx);
   const navigate = useNavigate();
-  const goBack = () => navigate(-1);
+  const goBack = onEscape ?? (() => navigate(-1));
 
   return (
     <PaginatedTablePicker

src/components/RuntimePicker.tsx

@@ -27,6 +27,7 @@ export interface RuntimePickerProps extends ScreenProps {
   breadcrumb: string[];
   description?: string;
   onSelect: (runtimeId: string) => void;
+  onEscape?: () => void;
 }
 
 export function RuntimePicker({
@@ -35,10 +36,11 @@ export function RuntimePicker({
   breadcrumb,
   description,
   onSelect,
+  onEscape,
 }: RuntimePickerProps) {
   const opts = coreOptsFromCtx(ctx);
   const navigate = useNavigate();
-  const goBack = () => navigate("/" + breadcrumb.slice(0, -1).join("/"));
+  const goBack = onEscape ?? (() => navigate("/" + breadcrumb.slice(0, -1).join("/")));
 
   return (
     <PaginatedTablePicker

src/core/abortable.ts

@@ -0,0 +1,32 @@
+/**
+ * Relays `source` while making an in-flight read reject as soon as `signal` aborts.
+ *
+ * Aborts use `signal.reason` or an `AbortError` fallback. The rejection remains
+ * observed when no read is pending, and source cleanup is fire-and-forget because
+ * a stalled stream may also stall `iterator.return()`.
+ */
+export async function* abortable<T>(
+  source: AsyncIterable<T>,
+  signal: AbortSignal,
+): AsyncGenerator<T> {
+  let abort = () => {};
+  const aborted = new Promise<never>((_, reject) => {
+    abort = () =>
+      reject(signal.reason ?? new DOMException("The operation was aborted", "AbortError"));
+    if (signal.aborted) abort();
+    else signal.addEventListener("abort", abort, { once: true });
+  });
+  aborted.catch(() => {});
+
+  const iterator = source[Symbol.asyncIterator]();
+  try {
+    for (;;) {
+      const result = await Promise.race([iterator.next(), aborted]);
+      if (result.done) return;
+      yield result.value;
+    }
+  } finally {
+    signal.removeEventListener("abort", abort);
+    void iterator.return?.()?.catch(() => {});
+  }
+}