Skip to content

Commit 0da5441

Browse files
Update docs/design/AgentRun-CLI-Design.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
1 parent 8ea9a5a commit 0da5441

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/design/AgentRun-CLI-Design.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ A developer wants to create a new agent from scratch and publish it to AgentCube
2121
After completing development, the CLI enables the following steps:
2222
1. `agentrun pack -f ./` Packages the agent source code and runtime metadata into a structured workspace directory, preparing it for image creation
2323
2. `agentrun build -f ./` Builds a container image from the workspace, compatible with AgentCube’s Kubernetes-based runtime environment
24-
3. `agentrun publish -f /` Publishes the built agent image to AgentCube, making it available for invocation, sharing, and collaboration
24+
3. `agentrun publish -f ./` Publishes the built agent image to AgentCube, making it available for invocation, sharing, and collaboration
2525

2626
Use Case 2: Check Published Agent Status
2727
After publishing an agent to AgentCube, a developer may want to verify that the agent is fully registered and ready for use. The CLI provides a simple status check command:

0 commit comments

Comments
 (0)