Install Tabbit Browser to review a signed-in dashboard with Solar Mini 4. Use a local agent that can select Upstage’s solar-mini4 and run Tabbit CLI. Ask it for changes within one date range, then review a named draft beside the source page. Upstage model documentation
A Reddit announcement about Solar Mini 4 in Cline drew interest in running the model through an agent client. That does not establish availability in your client. Original r/Cline discussion.
Key takeaways
Solar Mini 4 is the model, not the browser connection.
Check model access, client skill discovery, and local CLI reachability separately.
Sign in yourself in the intended Tabbit Browser profile.
Keep the first task read-only and require evidence.
What the official model page confirms
The official model page documents the provider’s model identifier and listed capabilities. It does not certify that your account, agent client, or browser connection can use the model. For Solar Mini 4 model background, see the provider’s model page and existing Tabbit setup guides. Do not confuse model support for tool calling with a working local browser route.
| Check | Proves | Does not prove |
|---|---|---|
| Model appears in picker | Client knows a model label | Account access or successful request |
| Short model request succeeds | Provider credentials and routing work | Tabbit CLI is connected |
| Tabbit skill runs | Client can reach local launcher | Site is signed in |
| Page values include IDs and URLs | Claims can be checked | Permission to make changes |
Prepare Tabbit Browser
Install Tabbit Browser and sign in to the target site yourself. Install the Tabbit skill where your local client discovers skills. Pi uses /skill:tabbit; some clients use /skills. Finding the skill and launching the CLI are separate checks. Use a separate task tab to keep your ordinary research tabs available. A cloud agent needs a separately supported local handoff; otherwise ask it to prepare steps for a local client. See the Tabbit CLI guide, browser connection guide, login reuse guide, and first-task checklist.
Use Solar Mini 4 to review dashboard changes
The task is to review a small date range in a dashboard and report what changed. Do not edit or export data. Keep the example separate from any customer or production data. The project’s local Tabbit fixture showed that a second task tab could read a signed-in test page after login. That verifies session reuse in the fixture only; it was not a model-specific run.
Use Tabbit CLI in the current Tabbit Browser profile. Read the dashboard change log for [DATE RANGE]. Do not edit, acknowledge, export, or submit anything. Return each visible row label, date, before/after value if shown, and source URL. List any field you could not verify. Save the report as “Solar dashboard changes” in the agreed draft and show it in the browser for my review.Expected output is a concise evidence table: visible label, value, record ID where applicable, and source URL. Example values are placeholders, not a recorded model run. If a field cannot be checked on the page, leave it unresolved.
| Stage | Pass evidence | Stop and inspect when |
|---|---|---|
| Model | The intended provider returns a response | Model ID is missing or access is denied |
| Client | Tabbit CLI opens a task tab | Skill appears but launcher fails |
| Page | Expected account and content are visible | Login page or unexpected account appears |
| Result | Each field maps to a visible source | IDs, dates, or units disagree |
Keep a human checkpoint
| Action | Agent role | Human review |
|---|---|---|
| Read page | Extract named visible fields | Confirm the account and page |
| Explain | Draft a short summary | Check definitions and context |
| Fill test form | Enter reviewed values only | Compare each field with source |
| Submit or edit live data | Stop before action | Approve and perform the change |
Solar Mini 4 can be evaluated for this bounded read if the model and local CLI both work in your client. Its official tool-calling support does not guarantee correct extraction or permission to act. For the choice between a browser integration and a remote tool, read browser MCP versus CLI. The related Codex setup guide, browser safety guide, local browser-agent guide, and AI browser workflow guide provide additional context.
FAQ
Can the model open a signed-in browser by itself?
No. A local agent client and browser integration are required.
How do I invoke the Tabbit skill?
Pi uses `/skill:tabbit`. Other clients may show a `/skills` picker or their own documented entry point.
Will Tabbit CLI sign in for me?
No. Sign in yourself in the selected Tabbit Browser profile first.
Can I use a remote agent?
Only if it has a supported local handoff. Otherwise pass its checklist to a local client.
What should the first task do?
Read a small, authorized page and return source URLs and visible identifiers.
Should the agent submit changes?
Keep the first run read-only. Review any proposed changes before applying them.