Configure coding agents
Choose where a coding agent belongs
Understand personal, organization, and project coding-agent ownership and the entries available when work is queued.
Choose the narrowest scope that serves the people who need the command. A definition stores its name, optional description, literal command template, and enabled state. It is not a hosted agent and alterac.ai never takes over the command's local permissions.
| Scope | Create it at | Who can use it |
|---|---|---|
| Personal | Your account's Coding agents page | You, in organizations that allow personal coding agents |
| Organization | The organization's Coding agents page | Members in the organization and its projects |
| Project | The project's Coding agents page | Members of that project |
There are no platform-owned coding-agent definitions in the current catalog. An organization entry is inherited by its projects; a project can hide an inherited organization entry only when organization policy allows it. Hiding changes availability in that project, not the organization entry or another project's view.
An enabled definition can appear in new selections. Disabling an entry keeps it at its owning scope but removes it from new selections. A project hide keeps the inherited organization definition intact and affects only that project. Deleting permanently removes an entry you own; it clears organization and project defaults that pointed to it. When you delete your personal default, alterac.ai instead makes the first remaining personal entry your default, if one exists. Deletion does not remove entries in other scopes.
Queueing makes a separate snapshot. Editing, disabling, hiding, or deleting a definition later does not change a command already queued or running.
The current settings pages do not offer a copy action. To reuse a definition at another scope, create a new entry, copy the literal command template yourself, give it a distinct name, and verify it before saving. The new definition is independent: later edits, disablement, hiding, or deletion do not affect the source entry.
Use command-template rules to validate the copied command, and use defaults and inheritance to decide which available entry should be selected automatically.