Manage configurations
Finding one
Three controls narrow the list, and they work together.
| Control | Options | Use it to |
|---|---|---|
| Search | free text | Match on name or display name |
| Source | All sources · This project · Provided by qRaptor | Separate your own configurations from the platform’s |
| Status | Active · Disabled · Any status | Find something you took out of service |
Underneath, the category tabs filter by kind — All, Models, Embeddings, Databases, Voice, Image & Video, Integrations. The count on each tab reflects the search and filters above it, so All is always the sum of the rest.
The status filter defaults to Active, which is why a configuration you disabled seems to vanish. Switch to Disabled or Any status to find it again.
What a card tells you
Each card shows the configuration’s name, the template it came from, a category chip, and the first few field values. Encrypted fields show a lock and a row of dots, and the card carries a N secrets badge. A System badge marks a platform configuration; those have no actions.
Any value on a card can be copied with the button beside it.
Editing
Open it
Use the ⋯ menu on the card and choose Edit. Developer Developer or above.
Change what you need
Everything is editable except the name. Encrypted fields arrive pre-filled with a placeholder — leave them alone to keep the stored secret, or type a new value to replace it. See Secrets & encryption.
Save changes
Changes take effect on the next run of anything that uses the configuration. There’s nothing to redeploy.
Disabling instead of deleting
The destructive action on a configuration is Disable, not delete. A disabled configuration:
- stops being usable by agents,
- keeps all its values, including its secrets,
- can be re-enabled at any time.
Disable
⋯ → Disable, then confirm. The dialog spells out what happens and where to find it afterwards.
Find it again
Set the Status filter to Disabled. Disabled cards are dimmed and carry a Disabled badge.
Re-enable
⋯ → Enable on the disabled card. It returns to service immediately.
Disabling a configuration that agents depend on will make them fail when they next try to use it. Check what references it first — the reference is the configuration’s name, so searching your tools for {{config.<type>.<name> finds the users.
Common issues
- A configuration disappeared from the list — it’s almost certainly disabled. Set Status to Any status.
- You can’t edit a configuration — either you’re a Viewer, or it’s provided by qRaptor. Platform configurations are read-only by design; see Models provided by qRaptor.
- The category tab shows a count you don’t expect — the counts respect the search and the source and status filters. Clear those to see everything.
- An agent stopped working after an edit — check the field the agent references still exists and still has a value. Editing a template’s optional fields to empty removes them.
Next
- Models provided by qRaptor — what you get without configuring anything.