Tabbit
ResourcesBlogModels
Tabbit LogoTabbit

Tabbit — The AI Browser that Works for You

Topics

  • Best Browsers 2026: Rankings and Top Lists
  • AI Browser Guides and Resources
  • Browser Comparisons: Head-to-Head Guides
  • Browser Reviews and Explainers
  • Browser Alternatives
  • Browser Directory: Guides by Browser
  • Agentic Browser Resources
  • Browser Downloads and Install Guides
  • Browser Productivity Resources
  • SillyTavern Model Guides and Presets

Popular Guides

  • Best Browsers 2026: Top 10 Ranked & Compared
  • Best Free AI Browsers 2026: Plans & Prices Compared
  • Rabbit Browser: What It Is & Why Tabbit Is Better
  • Firefox vs Chrome 2026: Privacy, RAM & Speed Compared
  • Best Lightweight Browsers 2026: 7 Tested for RAM & Speed
  • AI Browser List 2026: 10 Browsers Compared
  • Neobrowser: Norton Neo, Download & Alternatives
  • Edge vs Chrome 2026: Speed, RAM & Battery Tested
  • Best Internet Browser for Android 2026
  • Best AI Browser 2026: Top 9 Tested & Ranked

Events

  • Tabbit Skill Competition
  • KPOP SBTI Fandom Personality Test
  • Tabbit Campus Creator Program
  • fifi's Picks: AI Skills for Research Papers
  • User Survey

About

  • Tabbit Blog
  • Press & Media
English
简体中文English
Showcases & prompts

Kimi K3 · Workflow

Use Kimi K3 with OpenCode and Firecrawl for sourced web research

Connect Kimi K3, OpenCode, and Firecrawl MCP into a cited web-research workflow with explicit domains, permissions, and stop rules.

Source reviewed; not testedOpenCode + Firecrawl MCP/CLI + a Kimi K3 route; recheck terminal compatibility, especially on Windows.

Prerequisites and inputs

  • Research question
  • Allowed domains
  • MCP configuration
  • Stop and citation rules

Execution path

  1. Freeze the research question and allowed domains, and confirm fetching permission and sensitive-data boundaries.

  2. Configure the Kimi K3 route in OpenCode and register Firecrawl MCP/CLI; keep secrets in environment variables.

  3. Ask the agent to plan queries and page targets, then fetch pages while retaining URL, title, and collection time.

  4. Keep a source passage for every conclusion. Stop inference when a tool fails, a page is unreadable, or evidence conflicts.

  5. Run a final checklist for citation coverage, factual boundaries, and the deliverable before ending the loop.

Boundary

This is a complete external case study, not evidence of built-in Tabbit web access. Current OpenCode, Firecrawl, Kimi routing, and pricing remain unverified.

Read the source research notes

One-sentence takeaway

This complete case study connects Kimi K3 to OpenCode and Firecrawl MCP, allowing it to call live web search during long-running coding and research tasks.

Use cases

  • Suitable tasks: Tasks that require current web sources, long-context codebases, browser automation, or research-oriented agents.

  • Unsuitable tasks: Short answers that do not need web access, and environments with hard requirements for a stable native Windows terminal where WSL cannot be used.

  • Applicable model version: moonshotai/kimi-k3; the article also says that the weights were released on 2026-07-27.

  • Applicable client, agent, or API: OpenCode, Firecrawl CLI/MCP, OpenRouter, or another Kimi K3 provider.

  • Recommended reasoning tier and parameters: The article does not provide fixed parameters; for long-running agent tasks, use K3’s default thinking mode and let the harness manage the tool loop.

Ready-to-use content

Installation and launch:

npm install -g opencode-ai
opencode auth login
opencode

npm install -g firecrawl-cli
firecrawl setup mcp
firecrawl launch opencode

Verify MCP in OpenCode:

do a search for the latest news using the firecrawl mcp

Test/workflow steps

  1. Install OpenCode and log in to the selected model provider, confirming that the model name is moonshotai/kimi-k3.

  2. Install the Firecrawl CLI; run firecrawl setup mcp to write Firecrawl MCP into the OpenCode configuration.

  3. If the CLI refuses to write the API key to the client configuration after firecrawl login has been run, export FIRECRAWL_API_KEY instead, or launch with firecrawl launch opencode.

  4. Restart OpenCode so Kimi K3 can discover the MCP tools.

  5. Use the test request above to trigger a search; check that the model actually calls Firecrawl instead of answering from memory.

  6. For research tasks, add output constraints requiring sources and dates and requiring uncertainty to be stated explicitly, then save the search results and final deliverable.

Original evidence and data

  • The article explicitly provides commands for OpenCode, the Firecrawl CLI, setup mcp, and launch opencode, along with one web-search request.

  • The article says K3 can obtain live web data through Firecrawl MCP; it does not provide an independent comparison of success rate, latency, or cost.

  • The native Windows workflow encountered problems, and the author recommends Ubuntu/WSL; this is an observation from the author’s environment, not a Kimi official compatibility commitment.

Scope and limitations

  • The article also promotes the Firecrawl service, and its web-access conclusion comes from a single case; it should not be treated as a controlled agent benchmark.

  • OpenCode, the Firecrawl CLI, the MCP schema, and provider versions were not fixed; record versions and routing when reproducing it.

  • MCP tools expand the data and operations accessible to the model. In production, configure domain, permission, budget, and human-approval boundaries.

Reproduction steps

Run the installation commands above in an isolated project directory and record the CLI/OpenCode versions. Run the same test request three times, saving tool-call logs, retrieved URLs, citations in the answer, total tokens, and the number of failed retries. Compare “without MCP” and “with MCP” groups to determine the actual benefit of the web-access tool.

Source excerpt or observation (brief excerpt for compliance only)

The original article says: “We got Kimi K3 running in OpenCode and gave it live web access using the Firecrawl MCP.”

Source and dates

Firecrawl Blog · Source date: 2026-08 · Edited: 2026-09-20

Read the original source
Variable checklist

No required variables

Related showcases & prompts

Break a Kimi K3 agent loop into controlled stepsSet up a Kimi K3 API and agent loopWrite Kimi API requests as testable tasksTurn requirements into reviewable code changes in nine steps

Related reviews

Knowledge-work quality is competitive, but cost and time per task are highOfficial cases show long-horizon potential and reproducibility limitsThe same K3 differed by 20 percentage points across eight harnessesKimi K3 code security evaluation: strong benchmarks do not guarantee precision

Read the full analysis

Pricing · English

Kimi K3 Pricing: API Costs, Subscriptions, and Budget Math

Kimi K3 pricing explained with official API rates, cache-write rules, current membership tiers, worked costs, and a practical choice framework.

Comparison · English

Qwen4-Max vs Kimi K3: Which Model Fits Your Work?

Compare exact model versions, published prices, context and a matched data-analysis test, then decide what still needs testing on your workload.

Kimi K3

Use Kimi K3 in Tabbit

Run this guide in the environment listed above. Downloading does not transfer the template or establish model availability for your account.