fix(invoke): show full session ID and print resume command on exit

[aidandaly24]

Description

The invoke TUI truncated the session ID to 8 characters (550e8400), making it impossible to copy the full UUID needed for agentcore invoke --session-id <id> to resume a session. Additionally, there was no guidance on how to resume a session after exiting.

This PR:

• Displays the full session ID in the TUI header instead of truncating to 8 chars
• Prints a colored resume command (agentcore invoke --session-id <full-uuid>) after TUI exit
• Uses Ink's unmount() instead of process.exit(0) for clean shutdown, which also fixes the update notifier not appearing on Esc exit

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

Manually tested all exit paths:

• Ctrl+C: Resume message and update notifier both display ✅

• Double Esc: Resume message and update notifier both display ✅

• agentcore invoke (direct): Works correctly ✅

• agentcore → invoke (TUI): Works correctly ✅

• Session resumption: Copied session ID from output, used --session-id flag to resume successfully ✅

• I ran npm run test:unit and npm run test:integ

• I ran npm run typecheck

• I ran npm run lint

• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-0.9.1.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-904-tarball/aws-agentcore-0.9.1.tgz

[jesseturner21]

The useEffect that sets the exit message will cause issues when InvokeScreen is used from the main TUI (agentcore → invoke → Esc → help → exit). The message is set as soon as a session is created, but it's never cleared when the user navigates away from the invoke screen. This means users will see "To resume this session..." even if they left invoke and did other things before exiting.

Options to fix:

1. Add a cleanup function to clear the message on unmount:

useEffect(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}return()=>clearExitMessage();},[sessionId]);

2. Only set the message when actually exiting (similar to how CreateScreen does it) - wrap the onExit prop to set the message before calling it:

consthandleExit=useCallback(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}onExit();},[sessionId,onExit]);

Then use handleExit instead of onExit throughout the component.

Option 1 is simpler but means the message won't show if the user navigates away and then exits. Option 2 ensures the message only shows when exiting directly from invoke, which matches the CreateScreen pattern.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	42.43%	7169 / 16895
🔵	Statements	41.84%	7602 / 18169
🔵	Functions	40.14%	1273 / 3171
🔵	Branches	41.02%	4803 / 11708

Generated in workflow #1872 for commit 318f690 by the Vitest Coverage Report Action

[notgitika]

LGTM

[aidandaly24]

Description

The invoke TUI truncated the session ID to 8 characters (550e8400), making it impossible to copy the full UUID needed for agentcore invoke --session-id <id> to resume a session. Additionally, there was no guidance on how to resume a session after exiting.

This PR:

• Displays the full session ID in the TUI header instead of truncating to 8 chars
• Prints a colored resume command (agentcore invoke --session-id <full-uuid>) after TUI exit
• Uses Ink's unmount() instead of process.exit(0) for clean shutdown, which also fixes the update notifier not appearing on Esc exit

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

Manually tested all exit paths:

• Ctrl+C: Resume message and update notifier both display ✅

• Double Esc: Resume message and update notifier both display ✅

• agentcore invoke (direct): Works correctly ✅

• agentcore → invoke (TUI): Works correctly ✅

• Session resumption: Copied session ID from output, used --session-id flag to resume successfully ✅

• I ran npm run test:unit and npm run test:integ

• I ran npm run typecheck

• I ran npm run lint

• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-0.9.1.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-904-tarball/aws-agentcore-0.9.1.tgz

[jesseturner21]

The useEffect that sets the exit message will cause issues when InvokeScreen is used from the main TUI (agentcore → invoke → Esc → help → exit). The message is set as soon as a session is created, but it's never cleared when the user navigates away from the invoke screen. This means users will see "To resume this session..." even if they left invoke and did other things before exiting.

Options to fix:

1. Add a cleanup function to clear the message on unmount:

useEffect(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}return()=>clearExitMessage();},[sessionId]);

2. Only set the message when actually exiting (similar to how CreateScreen does it) - wrap the onExit prop to set the message before calling it:

consthandleExit=useCallback(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}onExit();},[sessionId,onExit]);

Then use handleExit instead of onExit throughout the component.

Option 1 is simpler but means the message won't show if the user navigates away and then exits. Option 2 ensures the message only shows when exiting directly from invoke, which matches the CreateScreen pattern.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	42.43%	7169 / 16895
🔵	Statements	41.84%	7602 / 18169
🔵	Functions	40.14%	1273 / 3171
🔵	Branches	41.02%	4803 / 11708

Generated in workflow #1872 for commit 318f690 by the Vitest Coverage Report Action

[notgitika]

LGTM

[aidandaly24]

Description

The invoke TUI truncated the session ID to 8 characters (550e8400), making it impossible to copy the full UUID needed for agentcore invoke --session-id <id> to resume a session. Additionally, there was no guidance on how to resume a session after exiting.

This PR:

• Displays the full session ID in the TUI header instead of truncating to 8 chars
• Prints a colored resume command (agentcore invoke --session-id <full-uuid>) after TUI exit
• Uses Ink's unmount() instead of process.exit(0) for clean shutdown, which also fixes the update notifier not appearing on Esc exit

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

Manually tested all exit paths:

• Ctrl+C: Resume message and update notifier both display ✅

• Double Esc: Resume message and update notifier both display ✅

• agentcore invoke (direct): Works correctly ✅

• agentcore → invoke (TUI): Works correctly ✅

• Session resumption: Copied session ID from output, used --session-id flag to resume successfully ✅

• I ran npm run test:unit and npm run test:integ

• I ran npm run typecheck

• I ran npm run lint

• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-0.9.1.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-904-tarball/aws-agentcore-0.9.1.tgz

[jesseturner21]

The useEffect that sets the exit message will cause issues when InvokeScreen is used from the main TUI (agentcore → invoke → Esc → help → exit). The message is set as soon as a session is created, but it's never cleared when the user navigates away from the invoke screen. This means users will see "To resume this session..." even if they left invoke and did other things before exiting.

Options to fix:

1. Add a cleanup function to clear the message on unmount:

useEffect(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}return()=>clearExitMessage();},[sessionId]);

2. Only set the message when actually exiting (similar to how CreateScreen does it) - wrap the onExit prop to set the message before calling it:

consthandleExit=useCallback(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}onExit();},[sessionId,onExit]);

Then use handleExit instead of onExit throughout the component.

Option 1 is simpler but means the message won't show if the user navigates away and then exits. Option 2 ensures the message only shows when exiting directly from invoke, which matches the CreateScreen pattern.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	42.43%	7169 / 16895
🔵	Statements	41.84%	7602 / 18169
🔵	Functions	40.14%	1273 / 3171
🔵	Branches	41.02%	4803 / 11708

Generated in workflow #1872 for commit 318f690 by the Vitest Coverage Report Action

[notgitika]

LGTM

[aidandaly24]

Description

The invoke TUI truncated the session ID to 8 characters (550e8400), making it impossible to copy the full UUID needed for agentcore invoke --session-id <id> to resume a session. Additionally, there was no guidance on how to resume a session after exiting.

This PR:

• Displays the full session ID in the TUI header instead of truncating to 8 chars
• Prints a colored resume command (agentcore invoke --session-id <full-uuid>) after TUI exit
• Uses Ink's unmount() instead of process.exit(0) for clean shutdown, which also fixes the update notifier not appearing on Esc exit

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

Manually tested all exit paths:

• Ctrl+C: Resume message and update notifier both display ✅

• Double Esc: Resume message and update notifier both display ✅

• agentcore invoke (direct): Works correctly ✅

• agentcore → invoke (TUI): Works correctly ✅

• Session resumption: Copied session ID from output, used --session-id flag to resume successfully ✅

• I ran npm run test:unit and npm run test:integ

• I ran npm run typecheck

• I ran npm run lint

• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-0.9.1.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-904-tarball/aws-agentcore-0.9.1.tgz

[jesseturner21]

The useEffect that sets the exit message will cause issues when InvokeScreen is used from the main TUI (agentcore → invoke → Esc → help → exit). The message is set as soon as a session is created, but it's never cleared when the user navigates away from the invoke screen. This means users will see "To resume this session..." even if they left invoke and did other things before exiting.

Options to fix:

1. Add a cleanup function to clear the message on unmount:

useEffect(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}return()=>clearExitMessage();},[sessionId]);

2. Only set the message when actually exiting (similar to how CreateScreen does it) - wrap the onExit prop to set the message before calling it:

consthandleExit=useCallback(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}onExit();},[sessionId,onExit]);

Then use handleExit instead of onExit throughout the component.

Option 1 is simpler but means the message won't show if the user navigates away and then exits. Option 2 ensures the message only shows when exiting directly from invoke, which matches the CreateScreen pattern.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	42.43%	7169 / 16895
🔵	Statements	41.84%	7602 / 18169
🔵	Functions	40.14%	1273 / 3171
🔵	Branches	41.02%	4803 / 11708

Generated in workflow #1872 for commit 318f690 by the Vitest Coverage Report Action

[notgitika]

LGTM

[aidandaly24]

Description

The invoke TUI truncated the session ID to 8 characters (550e8400), making it impossible to copy the full UUID needed for agentcore invoke --session-id <id> to resume a session. Additionally, there was no guidance on how to resume a session after exiting.

This PR:

• Displays the full session ID in the TUI header instead of truncating to 8 chars
• Prints a colored resume command (agentcore invoke --session-id <full-uuid>) after TUI exit
• Uses Ink's unmount() instead of process.exit(0) for clean shutdown, which also fixes the update notifier not appearing on Esc exit

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

Manually tested all exit paths:

• Ctrl+C: Resume message and update notifier both display ✅

• Double Esc: Resume message and update notifier both display ✅

• agentcore invoke (direct): Works correctly ✅

• agentcore → invoke (TUI): Works correctly ✅

• Session resumption: Copied session ID from output, used --session-id flag to resume successfully ✅

• I ran npm run test:unit and npm run test:integ

• I ran npm run typecheck

• I ran npm run lint

• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-0.9.1.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-904-tarball/aws-agentcore-0.9.1.tgz

[jesseturner21]

The useEffect that sets the exit message will cause issues when InvokeScreen is used from the main TUI (agentcore → invoke → Esc → help → exit). The message is set as soon as a session is created, but it's never cleared when the user navigates away from the invoke screen. This means users will see "To resume this session..." even if they left invoke and did other things before exiting.

Options to fix:

1. Add a cleanup function to clear the message on unmount:

useEffect(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}return()=>clearExitMessage();},[sessionId]);

2. Only set the message when actually exiting (similar to how CreateScreen does it) - wrap the onExit prop to set the message before calling it:

consthandleExit=useCallback(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}onExit();},[sessionId,onExit]);

Then use handleExit instead of onExit throughout the component.

Option 1 is simpler but means the message won't show if the user navigates away and then exits. Option 2 ensures the message only shows when exiting directly from invoke, which matches the CreateScreen pattern.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	42.43%	7169 / 16895
🔵	Statements	41.84%	7602 / 18169
🔵	Functions	40.14%	1273 / 3171
🔵	Branches	41.02%	4803 / 11708

Generated in workflow #1872 for commit 318f690 by the Vitest Coverage Report Action

[notgitika]

LGTM

[aidandaly24]

Description

The invoke TUI truncated the session ID to 8 characters (550e8400), making it impossible to copy the full UUID needed for agentcore invoke --session-id <id> to resume a session. Additionally, there was no guidance on how to resume a session after exiting.

This PR:

• Displays the full session ID in the TUI header instead of truncating to 8 chars
• Prints a colored resume command (agentcore invoke --session-id <full-uuid>) after TUI exit
• Uses Ink's unmount() instead of process.exit(0) for clean shutdown, which also fixes the update notifier not appearing on Esc exit

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

Manually tested all exit paths:

• Ctrl+C: Resume message and update notifier both display ✅

• Double Esc: Resume message and update notifier both display ✅

• agentcore invoke (direct): Works correctly ✅

• agentcore → invoke (TUI): Works correctly ✅

• Session resumption: Copied session ID from output, used --session-id flag to resume successfully ✅

• I ran npm run test:unit and npm run test:integ

• I ran npm run typecheck

• I ran npm run lint

• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-0.9.1.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-904-tarball/aws-agentcore-0.9.1.tgz

[jesseturner21]

The useEffect that sets the exit message will cause issues when InvokeScreen is used from the main TUI (agentcore → invoke → Esc → help → exit). The message is set as soon as a session is created, but it's never cleared when the user navigates away from the invoke screen. This means users will see "To resume this session..." even if they left invoke and did other things before exiting.

Options to fix:

1. Add a cleanup function to clear the message on unmount:

useEffect(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}return()=>clearExitMessage();},[sessionId]);

2. Only set the message when actually exiting (similar to how CreateScreen does it) - wrap the onExit prop to set the message before calling it:

consthandleExit=useCallback(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}onExit();},[sessionId,onExit]);

Then use handleExit instead of onExit throughout the component.

Option 1 is simpler but means the message won't show if the user navigates away and then exits. Option 2 ensures the message only shows when exiting directly from invoke, which matches the CreateScreen pattern.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	42.43%	7169 / 16895
🔵	Statements	41.84%	7602 / 18169
🔵	Functions	40.14%	1273 / 3171
🔵	Branches	41.02%	4803 / 11708

Generated in workflow #1872 for commit 318f690 by the Vitest Coverage Report Action

[notgitika]

LGTM

[aidandaly24]

Description

The invoke TUI truncated the session ID to 8 characters (550e8400), making it impossible to copy the full UUID needed for agentcore invoke --session-id <id> to resume a session. Additionally, there was no guidance on how to resume a session after exiting.

This PR:

• Displays the full session ID in the TUI header instead of truncating to 8 chars
• Prints a colored resume command (agentcore invoke --session-id <full-uuid>) after TUI exit
• Uses Ink's unmount() instead of process.exit(0) for clean shutdown, which also fixes the update notifier not appearing on Esc exit

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

Manually tested all exit paths:

• Ctrl+C: Resume message and update notifier both display ✅

• Double Esc: Resume message and update notifier both display ✅

• agentcore invoke (direct): Works correctly ✅

• agentcore → invoke (TUI): Works correctly ✅

• Session resumption: Copied session ID from output, used --session-id flag to resume successfully ✅

• I ran npm run test:unit and npm run test:integ

• I ran npm run typecheck

• I ran npm run lint

• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-0.9.1.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-904-tarball/aws-agentcore-0.9.1.tgz

[jesseturner21]

The useEffect that sets the exit message will cause issues when InvokeScreen is used from the main TUI (agentcore → invoke → Esc → help → exit). The message is set as soon as a session is created, but it's never cleared when the user navigates away from the invoke screen. This means users will see "To resume this session..." even if they left invoke and did other things before exiting.

Options to fix:

1. Add a cleanup function to clear the message on unmount:

useEffect(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}return()=>clearExitMessage();},[sessionId]);

2. Only set the message when actually exiting (similar to how CreateScreen does it) - wrap the onExit prop to set the message before calling it:

consthandleExit=useCallback(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}onExit();},[sessionId,onExit]);

Then use handleExit instead of onExit throughout the component.

Option 1 is simpler but means the message won't show if the user navigates away and then exits. Option 2 ensures the message only shows when exiting directly from invoke, which matches the CreateScreen pattern.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	42.43%	7169 / 16895
🔵	Statements	41.84%	7602 / 18169
🔵	Functions	40.14%	1273 / 3171
🔵	Branches	41.02%	4803 / 11708

Generated in workflow #1872 for commit 318f690 by the Vitest Coverage Report Action

[notgitika]

LGTM

[aidandaly24]

Description

The invoke TUI truncated the session ID to 8 characters (550e8400), making it impossible to copy the full UUID needed for agentcore invoke --session-id <id> to resume a session. Additionally, there was no guidance on how to resume a session after exiting.

This PR:

• Displays the full session ID in the TUI header instead of truncating to 8 chars
• Prints a colored resume command (agentcore invoke --session-id <full-uuid>) after TUI exit
• Uses Ink's unmount() instead of process.exit(0) for clean shutdown, which also fixes the update notifier not appearing on Esc exit

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

Manually tested all exit paths:

• Ctrl+C: Resume message and update notifier both display ✅

• Double Esc: Resume message and update notifier both display ✅

• agentcore invoke (direct): Works correctly ✅

• agentcore → invoke (TUI): Works correctly ✅

• Session resumption: Copied session ID from output, used --session-id flag to resume successfully ✅

• I ran npm run test:unit and npm run test:integ

• I ran npm run typecheck

• I ran npm run lint

• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-0.9.1.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-904-tarball/aws-agentcore-0.9.1.tgz

[jesseturner21]

The useEffect that sets the exit message will cause issues when InvokeScreen is used from the main TUI (agentcore → invoke → Esc → help → exit). The message is set as soon as a session is created, but it's never cleared when the user navigates away from the invoke screen. This means users will see "To resume this session..." even if they left invoke and did other things before exiting.

Options to fix:

1. Add a cleanup function to clear the message on unmount:

useEffect(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}return()=>clearExitMessage();},[sessionId]);

2. Only set the message when actually exiting (similar to how CreateScreen does it) - wrap the onExit prop to set the message before calling it:

consthandleExit=useCallback(()=>{if(sessionId){constcyan='\\x1b[36m';constreset='\\x1b[0m';setExitMessage(`To resume this session, run: ${cyan}agentcore invoke --session-id ${sessionId}${reset}`);}onExit();},[sessionId,onExit]);

Then use handleExit instead of onExit throughout the component.

Option 1 is simpler but means the message won't show if the user navigates away and then exits. Option 2 ensures the message only shows when exiting directly from invoke, which matches the CreateScreen pattern.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	42.43%	7169 / 16895
🔵	Statements	41.84%	7602 / 18169
🔵	Functions	40.14%	1273 / 3171
🔵	Branches	41.02%	4803 / 11708

Generated in workflow #1872 for commit 318f690 by the Vitest Coverage Report Action

[notgitika]

LGTM