The profiles you start with
Chat is an ordinary profile file. You can edit it or delete it like any profile you create.
A profile only narrows what you can do. It never grants more than your own access, and your organization’s limits still apply on top. See How access works.
Pick a profile
Choose the profile in the chat composer’s profile menu before you send. A new session starts under the profile you picked. You can switch a session’s profile later. The switch, and any edit to the profile file, applies from your next prompt. A turn already running keeps the profile it started with. Only you choose. The agent can’t change its own session’s profile, so a restricted session can never raise its own access.Create a profile
1
Open the profile menu
In the chat composer, open the profile menu and select Create permission.
2
Name it
Use letters, digits,
., _, and -. The menu shows the name with each word capitalized, so read-only shows as Read Only.3
Set what it allows
The new profile opens from a template. Edit it as a form, or switch to YAML. Errors block saving. Warnings don’t, but read them: they flag grants that give more than they seem.
4
Choose it
Pick it from the profile menu for the session.
<name>.permission.yaml in your profile folder, /workspaces/user_<uid>/.scriptit/profiles/. A profile with errors stays in the menu, marked, and you can’t send under it until you fix it or choose another.
You can also ask the agent to write a profile with you. From a Full session it can save the file. From a restricted session it gives you the text to save yourself.
What a profile can say
Nothing is granted unless a rule grants it. A section you leave out grants nothing, except
agent_models, where leaving it out allows any model.
Every session can always read its own files and write its own data_files/ folder, whatever the profile says.
Grants that deserve a second look
The editor warns about two kinds of grant:- Effectively Full.
"*"on sessions or triggers lets the session prompt any session or create triggers that run with your full authority."*"on integrations lets it manage integrations and change the policies that limit them. - Write access to a workspace. A write grant into a workspace lets the session change scripts that later run with your full authority. If a web page or a message tricks the agent, it could change them.
How restricted work runs
Work under Full runs with your account’s full view of your environment. Work under a restricted profile runs in its own container, which sees only the folders the profile grants. It reaches the internet only if the profile grants a network. It installs no packages.Agents run inside their caller’s limits
An Agent has its own permission, written in its.agent.md definition or in a shared .permission.yaml file. When something calls the Agent, both apply: the caller’s profile and the Agent’s own permission. Every one of them must allow an action.
So an Agent never gets more than whatever called it. A Chat session that calls an Agent with write access still can’t write.