Ticket Directives
Ticket directives give MergeLoom explicit instructions for a single ticket. Use them when repository catalog defaults are not specific enough.
Put directives in the ticket description inside the first [JCA]...[/JCA]
block:
[JCA]work_repos=apicontext_repos=shared-docscontext_files=api:MERGELOOM.mdcontext_folders=api:src/billinginline_context=Use the existing retry policy from the billing service.provider=claude-apimodel=sonnet[/JCA]Supported Keys
Section titled “Supported Keys”| Key | Use it for |
|---|---|
work_repos | Select one or more writable repository aliases for the job. |
context_repos | Add read-only repository aliases as context. |
context_files | Point MergeLoom at specific files, usually alias:path. |
context_folders | Point MergeLoom at specific folders, usually alias:path. |
inline_context | Add short ticket-specific implementation context. |
provider | Request a provider profile where your workspace allows it. |
model | Request a model alias where your workspace allows it. |
Unknown keys are not a reliable way to control behavior. Use only documented keys.
Repository Aliases
Section titled “Repository Aliases”Repository aliases come from the Controller UI Repository Catalog.
If a workspace has more than one enabled work repository, use repo-<alias>
labels for normal routing or work_repos=<alias> in a directive when the
ticket needs explicit routing.
Compatibility forms repo=<alias> and repo:<alias> may be accepted by the
router, but repo-<alias> is the customer-facing label format.
Validation and Failure Modes
Section titled “Validation and Failure Modes”Directive resolution happens before the worker starts the job.
Common failures:
work_reposnames an unknown or disabled repository aliascontext_reposnames a repository not enabled as work or contextcontext_filesorcontext_folderspoints at an invalid pathprovidernames a provider that is not ready or not allowedmodelnames a model alias not allowed by the workspace plan or provider
When resolution fails, MergeLoom blocks the job before execution and records the error in controller-side activity or job detail.