halkyon/.vscode/tasks.json

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "serverpod_start",
      "type": "shell",
      "command": "serverpod",
      "args": ["--no-analytics", "start"],
      "options": {
        "cwd": "${workspaceFolder}/halkyon_learn_server",
        "env": {
          // Marks a `serverpod start` launched from the IDE, which is the
          // only kind that honors the Flutter device picked in VS Code. A run
          // started from a plain terminal carries no marker, so a device file
          // left behind by a session that was killed cannot retarget it.
          "SERVERPOD_LAUNCHED_FROM_IDE": "true"
        }
      },
      "isBackground": true,
      "presentation": {
        "reveal": "always",
        "panel": "dedicated"
      },
      // The TUI captures stdout, so we can't string-match for "ready". The
      // attach config polls vm-service-info.json for the actual readiness
      // signal; this matcher exists only to satisfy VS Code's requirement
      // that background tasks declare one. The pattern intentionally never
      // matches; begin/end patterns mark the task active+ready immediately.
      "problemMatcher": {
        "owner": "serverpod",
        "pattern": [
          {
            "regexp": "^(SERVERPOD_NEVER_MATCH):(\\d+):(.+)$",
            "file": 1,
            "line": 2,
            "message": 3
          }
        ],
        "background": {
          "activeOnStart": true,
          "beginsPattern": ".",
          "endsPattern": "."
        }
      }
    }
  ]
}