0 Fork 0

T

weidu12123andClaude Opus 4.8 21ac1dd4c5 feat: move MCP call log into its own settings section with full detail and filters

The call log was a bare table crammed into the MCP Server settings tab: no
way to read what an agent actually sent or got back, and no way to narrow
it down.

- mcp_calls gains a `result` column holding the full text returned to the
  agent (previously only a one-line summary survived). Args and result are
  each capped at 256 KiB, and hitting the cap writes the truncation notice
  into the body itself instead of hiding it behind a flag. Existing
  databases pick the column up via ALTER TABLE; old rows stay empty.
- GET /api/mcp-calls now filters by host, tool, ok, and a closed-open
  time range. Host matching expands comma-joined batch targets, so
  `vip-hk` finds "vip-hk,gateway,..." while `hk` still matches nothing.
- The list returns a 400-char args preview only; a new
  GET /api/mcp-calls/:id serves one record's full args and result, so a
  500-row view cannot pull hundreds of megabytes into the browser.
- Settings gets a fourth category, "调用记录": date range (local-day
  boundaries converted to UTC instants), host/tool/result selects, reset,
  and rows that expand into the complete args and result with copy
  buttons.

Verified on the running build against 686 existing records: host, tool,
result, date and combined filters all narrow correctly, and a 300 KB
output shows the in-body truncation note.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-10-16 08:02:36 +08:00

.cargo

feat: initial commit of vps-switch core modules and desktop frontend

2026-10-13 16:36:22 +08:00

assets

fix: stop MCP exec poll loop and add MCP call audit; Linux/VPS deploy support

2026-10-15 16:38:10 +08:00

docs

feat: add command blacklist guardrail for MCP command channels

2026-10-13 23:55:31 +08:00

frontend

feat: move MCP call log into its own settings section with full detail and filters