overlane task policy | Overlane Docs

Reads the project’s task requirement (default required: edits and mutating shell commands are refused without an active task) and writes it to .overlane/state/task-policy.json for the hooks.

Usage

overlane task policy

Examples

overlane task policy

Behavior

Effect: read (changes nothing).
Needs credentials: yes. Uses the network: yes.
Supports --dry-run: no. Accepts --force: no.
Machine-readable description: overlane schema task policy.

Result

With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.

{
  "type": "object",
  "properties": {
    "enforcement": {
      "type": "string",
      "enum": [
        "required",
        "relaxed"
      ]
    },
    "reason": {
      "type": "string"
    },
    "changedBy": {
      "type": "string"
    },
    "updatedAt": {
      "type": "string"
    },
    "localFile": {
      "type": "string"
    }
  },
  "required": [
    "enforcement",
    "localFile"
  ],
  "additionalProperties": false
}

See exit codes for the status the process returns.