# Reported issues for Trusty Squire

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [Trusty Squire](/mcp/trusty-squire).

## Most discussed

### [skill-harvester] weaviate — Weaviate Cloud

**Status**: running (first attempt)

## Recent attempts

_(none yet — first attempt in progress)_

[Read the thread](https://github.com/Trusty-Squire/trusty-squire/issues/61) · 2026-05-26 · closed · 2 comments

### Egress grant rate limiting: omit ≠ unlimited (default 1000/hr), and the 429 body says "concurrency_limit" for a rate limit

Hit while running a legitimate agent-loop workload (autonomous coding-agent eval sweep) through an egress grant.

**1. Omitted rate limit is not unlimited.** The MCP tool doc says limits are *"OPT-IN and UNLIMITED by default: … Omit them for no rate/spend limit"*, but `grant_app_access` with no `rate_limit_per_hour` returns grants with `"rate_limit_per_hour": 1000`. Either the server default should honor omit=unlimited, or the tool doc should say the default is 1000.

**2. Misleading error namin

[Read the thread](https://github.com/Trusty-Squire/trusty-squire/issues/331) · 2026-07-05 · closed · 1 comment

### feat(mcp): support Hermes Agent (Nous Research) as an install target

Add [Hermes Agent](https://github.com/nousresearch/hermes-agent) (Nous Research) — a self-hosted, MCP-native agent — as a `connect --target=` option.

**Config:** `~/.hermes/config.yaml`, `mcp_servers` map keyed by name; stdio entries use `command`/`args`/`env`/`enabled` (same shape family as the Goose YAML target).

**Done:**
- `hermes` AgentTarget in `apps/mcp/src/install/agents.ts` — merges into `mcp_servers.squire`, preserves other servers + prior env (present-flag wins / absent-flag preserv

[Read the thread](https://github.com/Trusty-Squire/trusty-squire/issues/329) · 2026-07-05 · closed · 1 comment

### operate_seal_vault_credential → 400 unsupported_credential_type for username_password credentials

## Summary
Sealing a `username_password` vault credential into browser-fill slots fails with `400 unsupported_credential_type`, forcing the operator to type the password in plaintext — which defeats the sealed-fill security guarantee.

## Repro
1. Store a login credential:
   `store_credential(service:"dsers", fields:{username, password}, auth_strategy:"username_password", login_hosts:["www.dsers.com","dsers.com","accounts.dsers.com"], signin_url:"https://www.dsers.com/application/login")`
   → 

[Read the thread](https://github.com/Trusty-Squire/trusty-squire/issues/326) · 2026-07-05 · closed · 1 comment

### Bot: filled signup form on wrong website (off-domain searcher + KNOWN_DOMAINS bypass)

## Repro

User ran `mcp connect --target=goose` then asked Trusty Squire to provision Railway. The bot:

1. Navigated to `railway.com/login` (correct — KNOWN_DOMAINS entry).
2. `looksLikeSignupPage()` returned false → fell back to Google search.
3. Google search returned a link to **`storysite-production.up.railway.app/signup/`** — a customer's hobby Django app hosted *on* Railway, not Railway itself.
4. Bot followed the link, filled the form, submitted it.
5. Created a junk account on someone e

[Read the thread](https://github.com/Trusty-Squire/trusty-squire/issues/4) · 2026-05-21 · closed · 1 comment

### mcp connect: cpSync fails on broken npx bin symlinks → falls back to cache path

## Repro

Tested with `0.6.14-rc.3` on Linux:

```
$ npx --yes --package=@trusty-squire/mcp@0.6.14-rc.3 mcp connect --target=goose
Setting up Trusty Squire on this machine
[trusty-squire] couldnt copy node_modules to ~/.trusty-squire/lib
  (ENOENT: no such file or directory, stat
   /home/lunchbox/.trusty-squire/lib/node_modules/.bin/yaml);
  using cache path. Re-run install if the MCP server stops working.
✓ Wrote Goose MCP config at /home/lunchbox/.config/goose/config.yaml
✓ Already provisione

[Read the thread](https://github.com/Trusty-Squire/trusty-squire/issues/3) · 2026-05-21 · closed · 1 comment

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/Trusty-Squire/trusty-squire/issues).