Skip to content

Pull Agent Config

POST
/api/v1/projects/{project_id}/agent-config/pull
curl --request POST \
--url https://aura-api-eu.strangeworks.com/api/v1/projects/example/agent-config/pull \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{ "from_deployment": "example", "instructions": true, "skills": true }'

Pull a deployment’s instructions and/or skills into this project’s deployment scope.

Config is separate from the workspace, so this is how a project takes the operator’s current rules without workspace/checkout overwriting work in flight. Replaces the deployment scope rather than merging into it, so a rule the deployment retired stops applying here too. The project’s own scope is untouched.

Under agent-config/ rather than beside the skills collection, where the verb would collide with /skills/{skill} and reserve its name as an unusable skill.

project_id
required
Project Id
string
Media typeapplication/json
PullConfigRequest

Which agent config to pull from a deployment into a project’s deployment scope.

Both default on, so the common “give me the operator’s current rules” needs no flags; either can be turned off to pull one kind without the other.

object
from_deployment
required
From Deployment
string
>= 1 characters
instructions
Instructions
boolean
default: true
skills
Skills
boolean
default: true

Successful Response

Media typeapplication/json
PullConfigResponse
object
from_deployment
required
From Deployment
string
objects
required
Objects
integer
Examplegenerated
{
"from_deployment": "example",
"objects": 1
}

Validation Error

Media typeapplication/json
HTTPValidationError
object
detail
Detail
Array<object>
ValidationError
object
ctx
Context
object
input
Input
loc
required
Location
Array
msg
required
Message
string
type
required
Error Type
string
Examplegenerated
{
"detail": [
{
"ctx": {},
"input": "example",
"loc": [
"example"
],
"msg": "example",
"type": "example"
}
]
}