Vector Pairing Issue

[kuynh]

I was able to go through all the steps that you mentioned in your homepage and powershell output but now am stuck on pairing vector to the wirepod. I've already connected vector with wireos to wifi and got his ip address and ssh key ready but when trying to connect to your wirepod, I get an issue of

not running (last error: Process exited with status 127, last step: generating new robot cert)

One thing I also want to ask, your github homepage steps mentions running the .\windows\initial-setup.ps1 script but the powershell does not.

I ran the initial-setup script anyways but would just like to clarify with you to follow which one.

[Gman0909]

Thanks for the detailed report — and good catch on the docs mismatch.

On initial-setup.ps1: the README is the correct path; the install script's printed steps were wrong (they told you to set up the wizard by hand in "server IP" mode and never mentioned initial-setup.ps1). Follow the README: start-vector.ps1 → initial-setup.ps1 → apply-wirepod-config.ps1 → pair. I've fixed the contradictory instructions in #5.

On Process exited with status 127 … generating new robot cert: that error comes from the SSH-setup tab, which SSHes into Vector and runs an install script on the robot itself. Exit 127 means the robot's shell couldn't find/run that script — it's a robot-side (WireOS) failure, not a problem with the server.

This stack is built for a stock-firmware Vector using the escape-pod flow (the normal "Setup with the app" path in the Robots tab), not the WireOS SSH path. If you flashed WireOS and want the SSH method, the 127 usually means the dev-unlock didn't fully take — re-running the unlock or re-flashing tends to clear it. But the simplest route with this setup is to use escape-pod pairing instead. I've added a note to the README (#5) spelling out the two methods.

[kuynh]

Thanks for your response. I'll remove wireos and flash the stock firmware to vector. I will update if everything works as intended.

[kuynh]

I've flashed the stock os back to vector and redid your steps but am still having the issue of

"Error logging in. The bot is likely unable to communicate with your wire-pod instance. Make sure you followed all of the steps and try again."

when pairing the bot to wire-pod.

I took a look at the supervisor log and noticed that vector-ai seems to be having issues. Could this be a reason why?

2026-06-01 11:48:03 [supervisor] === Vector Pod Supervisor starting ===
2026-06-01 11:48:03 [supervisor] job object created (children will be killed with the supervisor)
2026-06-01 11:48:05 [supervisor] mDNS advertising escapepod.local -> 10.0.0.179
2026-06-01 11:48:05 [supervisor] Ollama already running
2026-06-01 11:48:05 [supervisor] started vector-ai (pid 3444)
2026-06-01 11:48:05 [supervisor] started chipper (pid 5780)
2026-06-01 11:48:05 [supervisor] startup complete
2026-06-01 11:48:17 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:48:17 [supervisor] started vector-ai (pid 8972)
2026-06-01 11:48:17 [supervisor] Vector link lost — will reconnect when it returns
2026-06-01 11:48:29 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:48:29 [supervisor] started vector-ai (pid 10012)
2026-06-01 11:48:41 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:48:41 [supervisor] started vector-ai (pid 16156)
2026-06-01 11:48:53 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:48:53 [supervisor] started vector-ai (pid 10852)
2026-06-01 11:49:05 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:49:05 [supervisor] started vector-ai (pid 10568)
2026-06-01 11:49:17 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:49:17 [supervisor] started vector-ai (pid 17840)
2026-06-01 11:49:29 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:49:29 [supervisor] started vector-ai (pid 14520)
2026-06-01 11:49:41 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:49:41 [supervisor] started vector-ai (pid 14720)
2026-06-01 11:49:53 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:49:53 [supervisor] started vector-ai (pid 19800)
2026-06-01 11:50:05 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:50:05 [supervisor] started vector-ai (pid 20032)
2026-06-01 11:50:17 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:50:17 [supervisor] started vector-ai (pid 8548)
2026-06-01 11:50:29 [supervisor] vector-ai unhealthy — restarting
2026-06-01 11:50:29 [supervisor] started vector-ai (pid 11000)

When opening the vector-ai.log, it keeps repeating one line of C:\Users\dang\vector-pod\vector-ai\venv\Scripts\python.exe: No module named uvicorn

[Gman0909]

Fixed it (in #5): the Windows installer was running pip install with --quiet and never checking whether it succeeded, so a failed/partial dependency install slipped through and the installer still printed "vector-ai ready." That's exactly what leaves vector-ai crash-looping and the supervisor spamming "vector-ai unhealthy, and then restarting."

Immediate fix — install the missing deps into the venv, then restart the stack:

& "$env:USERPROFILE\vector-pod\vector-ai\venv\Scripts\python.exe" -m pip install -r "$env:USERPROFILE\vector-pod\vector-ai\requirements.txt"
.\windows\stop-vector.ps1
.\windows\start-vector.ps1

After that, vector-pod\vector-ai.log should no longer show the uvicorn error and the "unhealthy — restarting" loop in supervisor.log should stop.

But to set expectations: vector-ai is the LLM/conversation proxy on port 8000 — it's not in the pairing path. Pairing/activation is handled entirely by chipper on port 443, and your log shows chipper healthy (no "chipper unhealthy" lines). So fixing vector-ai will get conversations working, but the "Error logging in" at the Activate step is most likely a separate, chipper-side issue. To pin it down, could you grab:

1. vector-pod\chipper.log — the last ~50 lines right after you hit Activate (that's where the token/login exchange is logged).
2. Confirm you ran .\windows\initial-setup.ps1 and the web UI at http://localhost:8080 shows escape-pod mode (not "server IP" mode).
3. In an admin PowerShell: Get-NetFirewallRule -DisplayName "VectorPod-*" — confirm rules for 443/80/8084/8080 exist and are enabled.
4. Confirm Vector is on the 2.4 GHz band of the same LAN as the PC, and no VPN/Tailscale is active on the PC.

With the chipper log around the Activate attempt I can get a better idea of what's failing.

[kuynh]

I installed the missing deps and restarted with vector scripts but the both logs of supervisor and vector-ai still print out the same problem as before.

However, something did pop up after running your & "$env:USERPROFILE\vector-pod\vector-ai\venv\Scripts\python.exe" -m pip install -r "$env:USERPROFILE\vector-pod\vector-ai\requirements.txt".

The console had this:

PS C:\Users\huynh\Documents\VectorIntelligence-main> & "$env:USERPROFILE\vector-pod\vector-ai\venv\Scripts\python.exe" -m pip install -r "$env:USERPROFILE\vector-pod\vector-ai\requirements.txt"

Collecting fastapi==0.115.0 (from -r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 1))
Using cached fastapi-0.115.0-py3-none-any.whl.metadata (27 kB)
Collecting uvicorn==0.30.6 (from uvicorn[standard]==0.30.6->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 2))
Using cached uvicorn-0.30.6-py3-none-any.whl.metadata (6.6 kB)
Collecting httpx==0.27.2 (from -r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 3))
Using cached httpx-0.27.2-py3-none-any.whl.metadata (7.1 kB)
Collecting python-dotenv==1.0.1 (from -r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 4))
Using cached python_dotenv-1.0.1-py3-none-any.whl.metadata (23 kB)
Collecting pydantic==2.8.2 (from -r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 5))
Using cached pydantic-2.8.2-py3-none-any.whl.metadata (125 kB)
Collecting zeroconf==0.131.0 (from -r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 6))
Using cached zeroconf-0.131.0-cp314-cp314-win_amd64.whl
Collecting starlette<0.39.0,>=0.37.2 (from fastapi==0.115.0->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 1))
Using cached starlette-0.38.6-py3-none-any.whl.metadata (6.0 kB)
Collecting typing-extensions>=4.8.0 (from fastapi==0.115.0->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 1))
Using cached typing_extensions-4.15.0-py3-none-any.whl.metadata (3.3 kB)
Collecting annotated-types>=0.4.0 (from pydantic==2.8.2->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 5))
Using cached annotated_types-0.7.0-py3-none-any.whl.metadata (15 kB)
Collecting pydantic-core==2.20.1 (from pydantic==2.8.2->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 5))
Using cached pydantic_core-2.20.1.tar.gz (388 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... done
Collecting click>=7.0 (from uvicorn==0.30.6->uvicorn[standard]==0.30.6->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 2))
Using cached click-8.4.1-py3-none-any.whl.metadata (2.6 kB)
Collecting h11>=0.8 (from uvicorn==0.30.6->uvicorn[standard]==0.30.6->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 2))
Using cached h11-0.16.0-py3-none-any.whl.metadata (8.3 kB)
Collecting anyio (from httpx==0.27.2->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 3))
Using cached anyio-4.13.0-py3-none-any.whl.metadata (4.5 kB)
Collecting certifi (from httpx==0.27.2->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 3))
Using cached certifi-2026.5.20-py3-none-any.whl.metadata (2.5 kB)
Collecting httpcore==1.* (from httpx==0.27.2->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 3))
Using cached httpcore-1.0.9-py3-none-any.whl.metadata (21 kB)
Collecting idna (from httpx==0.27.2->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 3))
Using cached idna-3.17-py3-none-any.whl.metadata (6.4 kB)
Collecting sniffio (from httpx==0.27.2->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 3))
Using cached sniffio-1.3.1-py3-none-any.whl.metadata (3.9 kB)
Requirement already satisfied: ifaddr>=0.1.7 in C:\Users\huynh\vector-pod\vector-ai\venv\Lib\site-packages (from zeroconf==0.131.0->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 6)) (0.2.0)
Collecting colorama>=0.4 (from uvicorn[standard]==0.30.6->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 2))
Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB)
Collecting httptools>=0.5.0 (from uvicorn[standard]==0.30.6->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 2))
Using cached httptools-0.8.0-cp314-cp314-win_amd64.whl.metadata (3.7 kB)
Collecting pyyaml>=5.1 (from uvicorn[standard]==0.30.6->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 2))
Using cached pyyaml-6.0.3-cp314-cp314-win_amd64.whl.metadata (2.4 kB)
Collecting watchfiles>=0.13 (from uvicorn[standard]==0.30.6->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 2))
Using cached watchfiles-1.2.0-cp314-cp314-win_amd64.whl.metadata (5.0 kB)
Collecting websockets>=10.4 (from uvicorn[standard]==0.30.6->-r C:\Users\huynh\vector-pod\vector-ai\requirements.txt (line 2))
Using cached websockets-16.0-cp314-cp314-win_amd64.whl.metadata (7.0 kB)
Using cached fastapi-0.115.0-py3-none-any.whl (94 kB)
Using cached pydantic-2.8.2-py3-none-any.whl (423 kB)
Using cached uvicorn-0.30.6-py3-none-any.whl (62 kB)
Using cached httpx-0.27.2-py3-none-any.whl (76 kB)
Using cached python_dotenv-1.0.1-py3-none-any.whl (19 kB)
Using cached httpcore-1.0.9-py3-none-any.whl (78 kB)
Using cached starlette-0.38.6-py3-none-any.whl (71 kB)
Using cached anyio-4.13.0-py3-none-any.whl (114 kB)
Using cached annotated_types-0.7.0-py3-none-any.whl (13 kB)
Using cached click-8.4.1-py3-none-any.whl (116 kB)
Using cached colorama-0.4.6-py2.py3-none-any.whl (25 kB)
Using cached h11-0.16.0-py3-none-any.whl (37 kB)
Using cached httptools-0.8.0-cp314-cp314-win_amd64.whl (92 kB)
Using cached idna-3.17-py3-none-any.whl (65 kB)
Using cached pyyaml-6.0.3-cp314-cp314-win_amd64.whl (156 kB)
Using cached typing_extensions-4.15.0-py3-none-any.whl (44 kB)
Using cached watchfiles-1.2.0-cp314-cp314-win_amd64.whl (288 kB)
Using cached websockets-16.0-cp314-cp314-win_amd64.whl (178 kB)
Using cached certifi-2026.5.20-py3-none-any.whl (134 kB)
Using cached sniffio-1.3.1-py3-none-any.whl (10 kB)
Building wheels for collected packages: pydantic-core
Building wheel for pydantic-core (pyproject.toml) ... error
error: subprocess-exited-with-error

× Building wheel for pydantic-core (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [65 lines of output]
Python reports SOABI: cp314-win_amd64
Computed rustc target triple: x86_64-pc-windows-msvc
Installation directory: C:\Users\huynh\AppData\Local\puccinialin\puccinialin\Cache
Rustup already downloaded
Installing rust to C:\Users\huynh\AppData\Local\puccinialin\puccinialin\Cache\rustup
warn: It looks like you have an existing rustup settings file at:
warn: C:\Users\huynh\AppData\Local\puccinialin\puccinialin\Cache\rustup\settings.toml
warn: Rustup will install the default toolchain as specified in the settings file,
warn: instead of the one inferred from the default host triple.
warn: installing msvc toolchain without its prerequisites
info: profile set to minimal
info: setting default host triple to x86_64-pc-windows-msvc
warn: Updating existing toolchain, profile choice will be ignored
info: syncing channel updates for stable-x86_64-pc-windows-msvc
info: default toolchain set to stable-x86_64-pc-windows-msvc
Checking if cargo is installed
cargo 1.96.0 (30a34c682 2026-05-25)
Rust not found, installing into a temporary directory
Running maturin pep517 build-wheel -i C:\Users\huynh\vector-pod\vector-ai\venv\Scripts\python.exe --compatibility off
📦 Including license file LICENSE
ðŸ\x8d¹ Building a mixed python/rust project
ðŸ\x90\x8d Found CPython 3.14 at C:\Users\huynh\vector-pod\vector-ai\venv\Scripts\python.exe
🔗 Found pyo3 bindings
📡 Using build options features, bindings from pyproject.toml
Compiling target-lexicon v0.12.14
Compiling cc v1.0.101
Compiling once_cell v1.19.0
Compiling proc-macro2 v1.0.86
Compiling unicode-ident v1.0.12
Compiling autocfg v1.3.0
Compiling heck v0.5.0
Compiling version_check v0.9.4
Compiling libc v0.2.155
Compiling rustversion v1.0.17
Compiling static_assertions v1.1.0
Compiling cfg-if v1.0.0
Compiling radium v0.7.0
Compiling tinyvec_macros v0.1.1
Compiling memchr v2.7.4
Compiling tap v1.0.1
Compiling tinyvec v1.6.1
Compiling lexical-util v0.8.5
Compiling serde v1.0.203
Compiling wyz v0.5.1
error: linker link.exe not found
|
= note: program not found

  note: the msvc targets depend on the msvc linker but `link.exe` was not found

  note: please ensure that Visual Studio 2017 or later, or Build Tools for Visual Studio were installed with the Visual C++ option

  note: VS Code is a different product, and is not sufficient

  error: could not compile `radium` (build script) due to 1 previous error
  warning: build failed, waiting for other jobs to finish...
  error: could not compile `serde` (build script) due to 1 previous error
  error: could not compile `proc-macro2` (build script) due to 1 previous error
  error: could not compile `rustversion` (build script) due to 1 previous error
  error: could not compile `libc` (build script) due to 1 previous error
  error: could not compile `target-lexicon` (build script) due to 1 previous error
  💥 maturin failed
    Caused by: Failed to build a native library through cargo
    Caused by: Cargo build finished with "exit code: 101": `"cargo" "rustc" "--profile" "release" "--features" "pyo3/extension-module" "--message-format" "json-render-diagnostics" "--manifest-path" "C:\\Users\\huynh\\AppData\\Local\\Temp\\pip-install-b3tbt6ee\\pydantic-core_95c9d4759fb4438a86b1a0636914f4c7\\Cargo.toml" "--lib" "--crate-type" "cdylib"`
  Error: command ['maturin', 'pep517', 'build-wheel', '-i', 'C:\\Users\\huynh\\vector-pod\\vector-ai\\venv\\Scripts\\python.exe', '--compatibility', 'off'] returned non-zero exit status 1
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for pydantic-core
Failed to build pydantic-core
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> pydantic-core
PS C:\Users\huynh\Documents\VectorIntelligence-main>

---

I'm going to skip the chipper log for now since there are other issues to be solved first.

As for running Get-NetFirewallRule -DisplayName "VectorPod-*", this is printed out:

PS C:\WINDOWS\system32> Get-NetFirewallRule -DisplayName "VectorPod-*"

Name : {38ce22b2-9b30-41a8-9eab-0a25eb8ff15d}
DisplayName : VectorPod-443
Description :
DisplayGroup :
Group :
Enabled : True
Profile : Any
Platform : {}
Direction : Inbound
Action : Allow
EdgeTraversalPolicy : Block
LooseSourceMapping : False
LocalOnlyMapping : False
Owner :
PrimaryStatus : OK
Status : The rule was parsed successfully from the store. (65536)
EnforcementStatus : NotApplicable
PolicyStoreSource : PersistentStore
PolicyStoreSourceType : Local
RemoteDynamicKeywordAddresses : {}
PolicyAppId :
PackageFamilyName :

Name : {eeffafdb-80c0-4a15-a75c-e5f5d49616cc}
DisplayName : VectorPod-8080
Description :
DisplayGroup :
Group :
Enabled : True
Profile : Any
Platform : {}
Direction : Inbound
Action : Allow
EdgeTraversalPolicy : Block
LooseSourceMapping : False
LocalOnlyMapping : False
Owner :
PrimaryStatus : OK
Status : The rule was parsed successfully from the store. (65536)
EnforcementStatus : NotApplicable
PolicyStoreSource : PersistentStore
PolicyStoreSourceType : Local
RemoteDynamicKeywordAddresses : {}
PolicyAppId :
PackageFamilyName :

Name : {7719af8c-7059-482c-86ff-fe3452bf28f0}
DisplayName : VectorPod-80
Description :
DisplayGroup :
Group :
Enabled : True
Profile : Any
Platform : {}
Direction : Inbound
Action : Allow
EdgeTraversalPolicy : Block
LooseSourceMapping : False
LocalOnlyMapping : False
Owner :
PrimaryStatus : OK
Status : The rule was parsed successfully from the store. (65536)
EnforcementStatus : NotApplicable
PolicyStoreSource : PersistentStore
PolicyStoreSourceType : Local
RemoteDynamicKeywordAddresses : {}
PolicyAppId :
PackageFamilyName :

Name : {b1a42bb9-4a6b-4f5d-817f-fd26358a68eb}
DisplayName : VectorPod-8084
Description :
DisplayGroup :
Group :
Enabled : True
Profile : Any
Platform : {}
Direction : Inbound
Action : Allow
EdgeTraversalPolicy : Block
LooseSourceMapping : False
LocalOnlyMapping : False
Owner :
PrimaryStatus : OK
Status : The rule was parsed successfully from the store. (65536)
EnforcementStatus : NotApplicable
PolicyStoreSource : PersistentStore
PolicyStoreSourceType : Local
RemoteDynamicKeywordAddresses : {}
PolicyAppId :
PackageFamilyName :

PS C:\WINDOWS\system32>

I can confirm that my network is a 2.4 Ghz. I separated the two bands into two networks with specific names. There is also no VPN or tailscale installed on this computer.

[Gman0909]

Got it — and that pip output is the smoking gun. Thanks for pasting it in full.

The real root cause: your venv was built on Python 3.14. The give-aways:

Using cached zeroconf-0.131.0-cp314-cp314-win_amd64.whl
...
Found CPython 3.14 at C:\Users\huynh\vector-pod\vector-ai\venv\Scripts\python.exe
...
error: linker `link.exe` not found

pydantic-core==2.20.1 (pulled in by pydantic==2.8.2) doesn't ship a prebuilt wheel for 3.14, so pip fell back to compiling it from Rust source, which needs the MSVC C++ toolchain (link.exe) that isn't on your machine. The build fails, the install stops partway, and that's why uvicorn never landed → the crash loop. Re-running the installer couldn't fix it because it kept rebuilding the same 3.14 venv.

So my earlier exit-code change made the failure visible but didn't prevent it. The proper fix is to pin the venv to Python 3.11, where every dependency has a prebuilt wheel and nothing needs a compiler.

Immediate remedy (gets you running now, no compiler required):

# 1. Install Python 3.11 (it coexists fine with your 3.14)
winget install --id Python.Python.3.11 -e

# 2. Delete the broken 3.14 venv
Remove-Item -Recurse -Force "$env:USERPROFILE\vector-pod\vector-ai\venv"

# 3. Recreate it on 3.11 and install the deps
py -3.11 -m venv "$env:USERPROFILE\vector-pod\vector-ai\venv"
& "$env:USERPROFILE\vector-pod\vector-ai\venv\Scripts\python.exe" -m pip install -r "$env:USERPROFILE\vector-pod\vector-ai\requirements.txt"

# 4. Restart the stack
.\windows\stop-vector.ps1
.\windows\start-vector.ps1

(If step 3 says py -3.11 can't be found, open a fresh PowerShell window after step 1 so the launcher is on PATH.) After this, vector-ai.log should be clean and the "unhealthy — restarting" loop in supervisor.log should stop.

Permanent fix: #7 makes install.ps1 resolve Python 3.11 explicitly, install it if missing, build the venv with it, and auto-rebuild a wrong-version venv on re-run. Once it's merged, a git pull + re-run of install.ps1 repairs this automatically.

---

One important thing about the pairing error, so you're not chasing the wrong process: vector-ai is not in the pairing path. It's the LLM/conversation proxy on port 8000; pairing and the "Activate" login are handled entirely by chipper on port 443. Your supervisor log shows chipper coming up with no "chipper unhealthy" lines, so the Error logging in. The bot is likely unable to communicate with your wire-pod instance is almost certainly a separate, chipper-side issue that fixing vector-ai won't resolve.

That makes chipper.log the one thing I still need to get you paired — specifically the last ~50 lines right after you press Activate in the app. That's where the cert/token exchange between Vector and chipper is logged, and it'll tell us exactly what's rejecting the login. Everything else you've verified (firewall rules, 2.4 GHz band, no VPN) is spot on and rules out the usual suspects — so the chipper log is the next step whenever you're ready.

[kuynh]

Thanks for the lines above, no more issues pop up other than chipper now. As for the chipper.log file, when pressing activate after going through the setup of connecting vector, nothing pops up in the file. Only thing that shows is that chipper was able to launch successfully.

Commit SHA:
Initializing variables
SDK info path: C:\Users\huynh/.anki_vector/
API config successfully read
Reading session certs for robot IDs
Initiating whisper.cpp voice processor with language en-US
Opening Whisper model (..\whisper.cpp\models\ggml-base.en.bin)
whisper_init_from_file_with_params_no_state: loading model from '..\whisper.cpp\models\ggml-base.en.bin'
whisper_init_with_params_no_state: use gpu = 1
whisper_init_with_params_no_state: flash attn = 0
whisper_init_with_params_no_state: gpu_device = 0
whisper_init_with_params_no_state: dtw = 0
whisper_init_with_params_no_state: devices = 1
whisper_init_with_params_no_state: backends = 1
whisper_model_load: loading model
whisper_model_load: n_vocab = 51864
whisper_model_load: n_audio_ctx = 1500
whisper_model_load: n_audio_state = 512
whisper_model_load: n_audio_head = 8
whisper_model_load: n_audio_layer = 6
whisper_model_load: n_text_ctx = 448
whisper_model_load: n_text_state = 512
whisper_model_load: n_text_head = 8
whisper_model_load: n_text_layer = 6
whisper_model_load: n_mels = 80
whisper_model_load: ftype = 1
whisper_model_load: qntvr = 0
whisper_model_load: type = 2 (base)
whisper_model_load: adding 1607 extra tokens
whisper_model_load: n_langs = 99
whisper_model_load: CPU total size = 147.37 MB
whisper_model_load: model size = 147.37 MB
whisper_backend_init_gpu: no GPU found
whisper_init_state: kv self size = 6.29 MB
whisper_init_state: kv cross size = 18.87 MB
whisper_init_state: kv pad size = 3.15 MB
whisper_init_state: compute buffer (conv) = 16.26 MB
whisper_init_state: compute buffer (encode) = 85.86 MB
whisper_init_state: compute buffer (cross) = 4.65 MB
whisper_init_state: compute buffer (decode) = 96.35 MB
Loading plugins
Starting jdocs pinger ticker
Starting SDK app
Starting server at port 80 for connCheck
mDNS is disabled
BLE API is unregistered
Starting webserver at port 8080 (http://localhost:8080)
�[1;36mConfiguration page: http://10.0.0.179:8080�[0m
Initiating TLS listener, cmux, gRPC handler, and REST handler
Starting chipper server at port 443
Starting chipper server at port 8084 for 2.0.1 compatibility
�[33m�[1mwire-pod started successfully!�[0m

---

Supervisor.log file did output this small part but otherwise was successful as well.

2026-06-02 20:04:45 [supervisor] === Vector Pod Supervisor starting ===
2026-06-02 20:04:45 [supervisor] job object created (children will be killed with the supervisor)
2026-06-02 20:04:56 [supervisor] mDNS advertising escapepod.local -> 10.0.0.179
2026-06-02 20:04:58 [supervisor] started ollama (pid 10760)
2026-06-02 20:05:02 [supervisor] started vector-ai (pid 15264)
2026-06-02 20:05:02 [supervisor] started chipper (pid 11384)
2026-06-02 20:05:02 [supervisor] startup complete
2026-06-02 20:05:12 [supervisor] Vector link lost — will reconnect when it returns