Dayarc Upgrade

When to Use

User asks to update, upgrade, or check for new versions of the agent — including upgrading to a specific branch or commit, or returning to stable main.

Detecting Install Method

First, determine how Dayarc was installed:

# Check plugin install
$pluginHit = Get-ChildItem -Path (Join-Path $HOME ".copilot\installed-plugins") -Filter "plugin.json" -Recurse -ErrorAction SilentlyContinue | Where-Object {
    (Get-Content $_.FullName -Raw | ConvertFrom-Json).name -eq "dayarc"
} | Select-Object -First 1

# Check git clone
$cloneDir = Join-Path $HOME ".dayarc-agent"
$isClone = Test-Path (Join-Path $cloneDir ".git")

• Plugin install → $pluginHit exists → use copilot plugin update dayarc
• Git clone → $isClone is true → use git-based upgrade (below)
• Neither found → tell user to reinstall

Plugin Upgrade

If installed as a plugin, do not run the upgrade yourself. Plugin upgrades are managed by the Copilot CLI's built-in slash command, which only the user can invoke from chat. Instruct the user:

To upgrade the Dayarc plugin, run /plugin update dayarc in this chat. Once it finishes, ask me again and I'll re-register the scheduler if needed.

If the user reports the slash command has completed, run the After Update scheduler re-registration steps (skip the file-copy step — the plugin system handles that).

Preview branches are not supported for plugin installs. If the user asks for a preview branch, tell them to use the git clone install method instead.

Git Clone Upgrade

Detecting Preview Mode

Check whether ~/.dayarc-agent/.preview exists. If it does, warn the user:

⚠️ Preview build active — you are running a pre-release commit (<contents of .preview>). This build may be unstable. Say "upgrade to stable" to return to main.

Check for Updates

cd ~/.dayarc-agent
git fetch origin main

Compare HEAD vs origin/main:

• If identical → "Already up to date."
• If behind → show new commits: git log HEAD..origin/main --oneline