Split the Core/Web boundary: official /v1, one Core-key /core/v1 tree, Core-key executor credentials by SaladDay · Pull Request #128 · MiniMax-AI/OpenAgentCore

Serve exactly the pinned official routes under /v1

SaladDay

committed

023909e

Test the administrator Runtime observation list

SaladDay

committed

8724394

Hold /v1 fields and routes to the pinned SDK

SaladDay

committed

aab4d6e

Merge remote-tracking branch 'origin/main' into codex/core-web-boundary-p2b

SaladDay

committed

3908b76

Remove the startup configuration and history capability reads left without a route

SaladDay

committed

47e0e9e

Serve /core/v1 as one Core-key tree and issue executor credentials there

SaladDay

committed

20f4025

Forward every signed-in /core/v1 request from the console with the Core key

SaladDay

committed

3d53520

Give the Core clients their own /core/v1 request layer

SaladDay

committed

8af26ce

Generate the /core/v1 contract as core.openapi.yaml

SaladDay

committed

80cd357

Test that each credential works only in its own namespace

SaladDay

committed

d828a74

Document the three namespaces and the Core-key executor credentials

SaladDay

committed

2ed7318

Name the Core key in the machine connection contract

SaladDay

committed

4900b8c

Merge origin/main (Core-key sign-in #124, allocation phase time #123, #125)

SaladDay

committed

a6cbbda

Test executor credential key_id form and unknown-key rotation over HTTP

SaladDay

committed

6219ad0

Refuse executor credential issuance and rotation in an archived Project

SaladDay

committed

24c0b48

Say "Core key only" in the /core/v1 operation descriptions

SaladDay

committed

b734d51

Check executor credential writes in the agreed order

SaladDay

committed

8f4be65

Issue the release guide's executor credential with the Core key

SaladDay

committed

158f6b9

Treat CoreMetricsClient baseUrl as a prefix like the other Core clients

SaladDay

committed

09070b8

Add the node enrollment token to the credential matrix

SaladDay

committed

7dba5e7

Tag the Core execution configuration read like the other /core/v1 reads

SaladDay

committed

f2ab0ac

Read the console's data through Core's new routes

SaladDay

committed

f9e5996

Check the project reader against Core's client type

SaladDay

committed

b13f18c

Issue, rotate and revoke executor credentials from a self-hosted Session

SaladDay

committed

e56a5df

Rotate restores a revoked executor credential, as in Core

SaladDay

committed

b9dc469

Match Core's executor credential rules in the fixture

SaladDay

committed

144ed8b

Hide executor credential writes on an archived project

SaladDay

committed

6341375

Derive the fixture's error type as Core does

SaladDay

committed

de32aed

Describe the console's /core/v1 prefix forwarding in the Web docs

SaladDay

committed

5c93243

Never recover an executor credential the administrator already managed

SaladDay

committed

d766039

Reject a non-JSON executor credential body with 400, as Core does

SaladDay

committed

05aa4d7

Correct the executor credential rules in the Web docs

SaladDay

committed

f9b145c

Navigation Menu

Repository navigation

Split the Core/Web boundary: official /v1, one Core-key /core/v1 tree, Core-key executor credentials - #128

Split the Core/Web boundary: official /v1, one Core-key /core/v1 tree, Core-key executor credentials#128
SaladDay merged 32 commits into
mainfrom
codex/core-web-boundary

Commits on Sep 25, 2026

Serve exactly the pinned official routes under /v1

Test the administrator Runtime observation list

Hold /v1 fields and routes to the pinned SDK

Merge remote-tracking branch 'origin/main' into codex/core-web-boundary-p2b

Remove the startup configuration and history capability reads left without a route

Serve /core/v1 as one Core-key tree and issue executor credentials there

Forward every signed-in /core/v1 request from the console with the Core key

Give the Core clients their own /core/v1 request layer

Generate the /core/v1 contract as core.openapi.yaml

Test that each credential works only in its own namespace

Document the three namespaces and the Core-key executor credentials

Name the Core key in the machine connection contract

Merge origin/main (Core-key sign-in #124, allocation phase time #123, #125)

Test executor credential key_id form and unknown-key rotation over HTTP

Refuse executor credential issuance and rotation in an archived Project

Say "Core key only" in the /core/v1 operation descriptions

Check executor credential writes in the agreed order

Issue the release guide's executor credential with the Core key

Treat CoreMetricsClient baseUrl as a prefix like the other Core clients

Add the node enrollment token to the credential matrix

Tag the Core execution configuration read like the other /core/v1 reads

Read the console's data through Core's new routes

Check the project reader against Core's client type

Issue, rotate and revoke executor credentials from a self-hosted Session

Rotate restores a revoked executor credential, as in Core

Match Core's executor credential rules in the fixture

Hide executor credential writes on an archived project

Derive the fixture's error type as Core does

Describe the console's /core/v1 prefix forwarding in the Web docs

Never recover an executor credential the administrator already managed

Reject a non-JSON executor credential body with 400, as Core does

Correct the executor credential rules in the Web docs