Hengfei YangandClaude Opus 4.7
f897aa2cb2
## Summary - Render `summary.return_code`, `stdout_lines`, `stderr_lines`, and `truncated` in the chat tool-call details panel so CLI tool results show parsed info like MCP tools do. - Whitelist `command` in `getToolCallDisplayData` and add a "Command" row with a copy button so the actual CLI command the agent ran is visible. ## Context The o2-ai server already emits a uniform `tool_result` shape for CLI tools (see openobserve/o2-ai#96 — wait for that to merge): ```json { "type": "tool_result", "tool": "cli_kubectl", "success": true, "message": "Exited 0 (12 lines stdout)", "summary": { "return_code": 0, "stdout_lines": 12, "stderr_lines": 0 }, "call_args": { "command": "get pods -n default" }, "call_id": "call-uuid-v7" } ``` `ContentBlock.summary` was already being captured from the event — the template just had no conditionals for the CLI fields. This PR adds them. ## What this does NOT do - Does not show raw `stdout`/`stderr` text (server currently only sends line counts). If we want inline output, that's a separate backend change. - Does not add a custom header format for CLI — the default `block.message` ("Exited 0 (12 lines stdout)") renders fine as plain text. ## Test plan - [x] `npm run type-check` — clean - [ ] Manually verify in dev chat that a CLI tool call (`kubectl get pods`) shows the Exit code / Stdout / Stderr rows and the Command row with copy button - [ ] MCP tools (SearchSQL, StreamList) still render the existing Results / Duration rows unchanged 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
web
This template should help get you started developing with Vue 3 in Vite.
Recommended IDE Setup
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
Type Support for .vue Imports in TS
TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.
If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensionsfrom VSCode's command palette - Find
TypeScript and JavaScript Language Features, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Windowfrom the command palette.
Customize configuration
See Vite Configuration Reference.
Project Setup
npm install
Compile and Hot-Reload for Development
For stand-alone UI development environment, create .env file and which contains below environment variable
VITE_OPENOBSERVE_ENDPOINT=http://localhost:5080/
npm run dev
Type-Check, Compile and Minify for Production
npm run build
Run Unit Tests with Vitest
npm run test:unit
Run End-to-End Tests with Cypress
npm run test:e2e:dev
This runs the end-to-end tests against the Vite development server. It is much faster than the production build.
But it's still recommended to test the production build with test:e2e before deploying (e.g. in CI environments):
npm run build
npm run test:e2e
Lint with ESLint
npm run lint