Expose preview status/logs/restart tools to the AI chat

[pablopunk]

Summary

• New backend service + per-project token + internal API at /api/internal/ai-tools/preview/{status,logs,restart} that the chat agent can call to check the doce preview server, read its logs, and restart it
• Three OpenCode custom tools (get_doce_preview_status, read_doce_preview_logs, restart_doce_preview) generated at runtime into ${DATA_PATH}/opencode/tools/. Tools auto-resolve projectId + token from context.directory; no agent-visible internal IDs
• Chat tool registry: dropped colored icons and added a getDetails({input,output,status}) field so each tool defines its own concise expanded view instead of raw JSON dumps

Caveats

• OpenCode 1.14.48 currently crashes any custom tool that declares an args: field with undefined is not an object (evaluating 'g.split'). To work around it, the three tools take no arguments and use sensible defaults (logs always returns tail+signal; restart records a generic reason). Once that bug is fixed in opencode we can re-add typed args without other changes.

Test plan

• Open an existing project's chat, ask "Is the preview running?" — Preview Status tool call should render and the expanded panel should show a one-line summary
• Ask "Read the recent preview logs" — Preview Logs should return the last error signal + tail
• Manually break the preview (e.g. introduce a syntax error in src/pages/index.astro), then ask the agent to diagnose + fix — it should chain status → logs → restart as needed
• Verify no colored icons remain on any tool calls and no raw JSON Input: blocks appear in expanded views

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Added AI tools for preview status checks, log viewing, and restart capabilities
  • Enhanced tool call display with richer contextual details and metadata

• Documentation

  • Updated preview troubleshooting guide with improved tool usage recommendations

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
doce-dev-www	Ready	Preview, Comment	May 14, 2026 0:56am

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

This PR implements internal Doce preview tools for OpenCode that enable monitoring and management of Docker Compose preview services. It adds three new tools—get_doce_preview_status, read_doce_preview_logs, and restart_doce_preview—with per-project token authentication. The changes include token infrastructure, internal API endpoints, service logic for status/logs/restart operations, tool source code generation, OpenCode runtime integration, and documentation updates. The feature is wired into project setup and session creation flows.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 13.33% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Expose preview status/logs/restart tools to the AI chat' directly and clearly describes the main change: making three preview management tools (status, logs, restart) available to the AI chat agent.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}