docs: clarify Wanta open-source positioning

[alwaysmavs]

Summary

OpenConnector's README files previously described Wanta mainly as a hosted product entry point for trying SaaS connections. Since Wanta is now available as an open-source desktop Agent project, that framing no longer explained the relationship between the two repositories or the ways open-source users can run, adapt, and contribute to Wanta.

This change presents OpenConnector and Wanta as two projects in the same OOMOL open-source ecosystem. It explains that OpenConnector connects Agents to external services, while Wanta provides a complete desktop Agent application powered by OpenCode and uses OpenConnector for connected SaaS services.

The revised section gives readers three concrete paths:

• run Wanta locally with an OpenAI-compatible model and no Wanta account;
• fork and customize Wanta to build a desktop Agent;
• optionally use hosted models, OAuth connections, and team workspaces.

It also links Wanta's GitHub repository directly and invites issues and pull requests. The wording is synchronized across the English, Simplified Chinese, Traditional Chinese, French, Japanese, Korean, and Russian README files.

User impact

Readers can now understand what each project does, how the projects relate technically, and which parts can be used locally or customized. The section remains compact while providing enough context to avoid presenting Wanta only as a commercial or hosted path.

Validation

• npm run lint
• npm run fix-check
• git diff --check

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 36368d94-d014-4df9-885a-c33bdfacf845

📥 Commits

Reviewing files that changed from the base of the PR and between 0560a66 and 3797beb.

📒 Files selected for processing (7)

• README.md
• docs/README.fr.md
• docs/README.ja.md
• docs/README.ko.md
• docs/README.ru.md
• docs/README.zh-CN.md
• docs/README.zh-TW.md

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch codex/improve-wanta-open-source-description

---

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