Skip to main content

Inspect History in the console

Read the recorded State behind an AgentCore workload without changing it.

Implemented in sourceReviewed 2026-10-14 · prelaunchRead this guide as Markdown
Guide context

Inspect authorized State History from an AgentCore workload through read-only workspace, scope, UTC-day and exact-revision navigation.

Inspect the State History an AgentCore application recorded. A signed-in operator chooses an authorized workspace, scope and UTC date, then reads exact revisions from a fixed list. The console is read-only and never replaces a requested old version with a newer one.

On this page · 3 sections

Inspect an AgentCore workload's History

  1. Choose workspace and scope

    Use the server-authorized workspace and supplied subject and type.

  2. Pin UTC day and generation

    Keep membership fixed while reading more pages.

  3. Inspect the exact revision

    Read retained data and source references; the console executes no agent or tool.

Browse History like folders#

  1. Workspaces

    The History API lists the workspaces your account may read, with your role.

  2. Scope

    Enter the subject and record type supplied for your authorized workspace. The console does not invent a scope directory.

  3. UTC days

    Pick a month, then select today or one of the preceding 364 UTC dates. A date in this window is eligible for reads; its presence does not mean that the day’s records are complete.

  4. Exact records

    One page of a pinned generation is hydrated to exactly those revisions; the inspector adds timestamps, source references, and the record’s earlier revisions.

Sign in with your Kam account#

The console uses the Cognito client’s configured Amplify sign-in flow. Server settings choose email or username; they do not grant workspace access. The server reads the session, re-verifies the Cognito access token with AWS’s verifier, and calls the History API on your behalf. Which workspaces you see comes from the History API, never from the browser; a refusal is shown as access denied, never worked around.

What the console will not do#

  1. Write anything

    Only read routes are called. There is no outcome, configuration, deletion, or lifecycle action.

  2. Fall back to latest

    A changed generation or a revision that does not match the requested reference is an error, not a substitution.

  3. Read without bounds

    At most 32 references per read, only inside the 365-UTC-date window, and never a cursor without its generation.

Try the fixture inspector Read the History contract
Agent-readable documentation manifest