Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Support interactive TUI invocation for existing AgentCore Harnesses by ARN

未关闭
  • 哪里不对？
#2,008 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
aws, typescript
领域
cli

调研方向

该 payload 没有指出任何实现文件或测试。先从 agentcore invoke 入口及其现有的 --harness-arn 路径开始，然后跟踪 InvokeHarness 的流式处理流程。完成的标准是：由外部管理的 Harnesses 可以打开交互式聊天、复用或恢复会话、呈现流式输出，并在退出时报告会话 ID。

由索引模型根据 Issue 内容生成。

描述

enhancement
Description

AgentCore CLI should support opening the existing interactive chat/TUI experience against an already-deployed AgentCore Harness that was created outside the current AgentCore CLI project, such as a Harness created through the AWS Console, Terraform, CloudFormation, or the AgentCore control-plane API.

Today an externally managed Harness can be invoked with:

agentcore invoke \
  --harness-arn arn:aws:bedrock-agentcore:us-west-2:123456789012:harness/example \
  --region us-west-2 \
  --session-id <session-id> \
  "prompt"

However, --harness-arn is treated as a non-interactive option. Omitting the prompt results in:

No prompt provided. Usage: agentcore invoke --harness-arn <arn> --region <region> "your prompt"

This means users of externally managed Harnesses cannot use the CLI's interactive chat/TUI experience and instead have to repeatedly invoke the Harness with individual prompts or build their own frontend.

It would be useful to support something along the lines of:

agentcore invoke \
  --harness-arn <arn> \
  --region us-west-2 \
  --interactive

or, if no prompt is supplied and stdin is a TTY, automatically enter interactive mode:

agentcore invoke \
  --harness-arn <arn> \
  --region us-west-2

The interactive session should reuse a single runtimeSessionId for the duration of the session and allow an explicitly supplied --session-id so an existing Harness session can be resumed.

This would make the AgentCore CLI useful as a general client for managed Harnesses without requiring the Harness infrastructure to be owned or deployed by an AgentCore CLI/CDK project.

This is especially valuable for organizations that manage AgentCore infrastructure centrally with Terraform or CloudFormation while individual developers authenticate using their own AWS credentials.

Acceptance Criteria

  • agentcore invoke can enter an interactive terminal chat experience when targeting a Harness with --harness-arn.

  • The feature works without requiring an AgentCore CLI project or agentcore deploy.

  • The Harness may have been created by the AWS Console, Terraform, CloudFormation, or API.

  • An existing session can be resumed with:

    agentcore invoke \
  --harness-arn <arn> \
  --region <region> \
  --session-id <existing-session-id> \
  --interactive

  • Streaming assistant output is rendered interactively.

  • Exiting the TUI reports the session ID so the user can reconnect later.

Additional Context

A common deployment model is:

Terraform / CloudFormation / AWS Console
              |
              v
      AgentCore Harness
              ^
              |
      InvokeHarness API
              |
              v
        Developer CLI

In this model, the developer may have permission to invoke the Harness but intentionally does not have permission to deploy or modify it.

The existing CLI can already invoke such a Harness non-interactively:

agentcore invoke \
  --harness-arn <arn> \
  --region <region> \
  --session-id <session-id> \
  "prompt"

and --verbose exposes structured Harness streaming events such as toolUse and toolResult. The missing piece is an interactive frontend over the same invocation mechanism.

This would avoid teams having to build custom Harness clients solely to obtain a persistent terminal conversation and visibility into agent tool execution.

It would also make infrastructure ownership independent from developer UX: platform teams could manage Harnesses through their preferred IaC tooling while developers still get the native AgentCore interactive experience.

主要语言
TypeScript
星标
291
派生
96
平均合并
20 小时 50 分钟
30 天内合并 PR
214

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

aws/agentcore-cli 的其他 Issue

查看 aws/agentcore-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。