PROFILES
@forge/monorepo / backend/src / PROFILES
Variable: PROFILES
constPROFILES:object
Defined in: backend/src/capabilities/index.ts:98
Named starting points, so the two common shapes are one line.
A profile is only a set of defaults and must be expressible by writing the capabilities out — otherwise it
is a second configuration language, and the two drift. profileToMap and a test hold that.
Type Declaration
assistant
readonlyassistant:object
A chat assistant: everything a person interacts with, on.
assistant.citations
readonlycitations:"on"="on"
assistant.compaction
readonlycompaction:"on"="on"
assistant.guardrails
readonlyguardrails:"off"="off"
assistant.history
readonlyhistory:"on"="on"
assistant.mcp
readonlymcp:"off"="off"
assistant.memory
readonlymemory:"on"="on"
assistant.questions
readonlyquestions:"on"="on"
assistant.shell
readonlyshell:"off"="off"
assistant.skills
readonlyskills:"on"="on"
assistant.usage
readonlyusage:"on"="on"
automation
readonlyautomation:object
A headless automation: no conversation, no person, no recall.
usage stays on because an automation that runs unattended is precisely the one whose spend nobody is
watching. Turning metering off by default there would be the expensive mistake.
automation.citations
readonlycitations:"off"="off"
automation.compaction
readonlycompaction:"off"="off"
automation.guardrails
readonlyguardrails:"off"="off"
automation.history
readonlyhistory:"off"="off"
automation.mcp
readonlymcp:"off"="off"
automation.memory
readonlymemory:"off"="off"
automation.questions
readonlyquestions:"off"="off"
automation.shell
readonlyshell:"off"="off"
automation.skills
readonlyskills:"off"="off"
automation.usage
readonlyusage:"on"="on"