← Back to list
01Issue
FeatureOpenPlatformPublic
AssigneesNone
Relationships
#4827 Manage the swamp-club profile from an extension behavior: a profile API and a token scope
Opened by dmc · 11/17/2026
Problem
I can change my swamp-club profile only in the web profile editor. I keep the rest of my setup as code in a swamp repo: behaviors, workflows, vaults and serve configuration. The profile is the only part that I must edit by hand. I cannot review a profile change, keep a history of it, or apply it again from the repo.
Proposed solution
Let an extension behavior read and update the profile of the signed-in user.
- A profile API. One call reads the editable fields (for example Lore). One call updates them. The API applies the same validation as the editor, for example the 160-character limit on Lore (#4421). It rejects a bad value with a clear error. It does not cut the text.
- A token scope for the API, in the model of #960: for example
profile:readandprofile:write. A token withoutprofile:writecannot change the profile. A collective token cannot change a personal profile. - Documented authentication for extensions. Show how an extension calls the API with a scoped token from a vault, so that the extension does not read the credential file of
swamp auth login. - Optional: an official behavior (for example
@swamp/club-profile) with two methods:get: writes the current profile as data.update: takes the wanted field values. WithdryRunit shows the difference only. Without it, it applies the change.
Alternatives
- Use the web editor (the current method). There is no history and no review.
- Call the web endpoints that the editor uses. They are not documented, they can change without notice, and they need a browser session.
Security
- A change needs the write scope. A read of a field that is not public needs the read scope.
- Record each profile change, with the token that made it, so that the owner can see it.
02Bog Flow
Open
No activity in this phase yet.
03Sludge Pulse
Sign in to post a ripple.