Step 3.7 Flash is an open-weight StepFun model, distinct from the later Step 5 Preview. The Hugging Face model card lists Apache-2.0, and the official platform lists Step 3.7 Flash as an available model. The exact hosted route and client support can change, so check the provider’s model picker before you start. The Step 5 Preview entry and ID are separate. Do not substitute one for the other in a reproducible task.
Key takeaways
The model proposes; the local client manages tools and permissions.
Tabbit Browser supplies the browser environment. Tabbit CLI exposes a task tab to a compatible local agent.
Check the exact model route and the actual browser account before the task.
Start read-only. Leave a named draft and check every cited page.
Pick the model route before opening the page
| Check | Step 3.7 Flash | Browser task requirement |
|---|---|---|
| Model access | Confirm exact ID and provider in the client | Not provided by the browser |
| Execution | Provider-hosted inference; published weights also exist | Local agent must run the Tabbit CLI |
| Version boundary | Step 3.7 Flash is separate from Step 5 Preview | Do not substitute versions silently |
| Login context | Not part of the model endpoint | Confirm the account in Tabbit Browser |
| Browser checkpoint | Record in the draft | Stop condition |
|---|---|---|
| Identity | Stable record ID and URL | ID is missing or differs |
| Evidence | Visible value and page URL | Value is guessed |
| Permission | Read-only comparison | Save, send, or update requested |
Step 3.7 Flash is an open-weight StepFun model, distinct from the later Step 5 Preview. The Hugging Face model card lists Apache-2.0, and the official platform lists Step 3.7 Flash as an available model. The exact hosted route and client support can change, so check the provider’s model picker before you start. The Step 5 Preview entry and ID are separate. Do not substitute one for the other in a reproducible task.
A safe first task: compare a dashboard record
Choose an approved, low-risk record with a stable ID. Confirm it in the Tabbit Browser yourself, then ask the local agent to inspect the visible status and updated date. The goal is a comparison note, not a site change. If the record ID differs, a field is missing, or a login prompt appears, the task should stop and report that boundary.
| Checkpoint | Keep in the draft | Stop for human review when |
|---|---|---|
| Record identity | Stable ID and page URL | ID is missing or differs |
| Each field | Visible value plus source URL | Value is inferred or stale |
| Result | Match, mismatch, or unknown | Page asks to save or submit |
| Next action | Named review note | Any change to the source system |
A prompt for a named review draft
Use this prompt with your own test record. It is a suggested workflow, not a report of a model benchmark or a completed test against a third-party account.
Task name: GEO-104 dashboard change review
Use Step 3.7 Flash in this local agent and the installed Tabbit skill. Open the two URLs I provide in a separate Tabbit task tab. Read only record ID, status, and updated date. For every value, include its source URL. Use unknown when a field is not visible. If the ID differs, a login screen or CAPTCHA appears, or the page offers a write action, stop and report it. Do not save, submit, send, or change anything. Leave a draft named “GEO-104 — dashboard change review” with matched fields, mismatches, unknowns, and the URLs for my review.Use the model you can actually select in a local agent client. Then connect that client to Tabbit CLI. The model does not supply the browser, login session, or permission boundary. Start with read-only inspection and leave a named draft for a person to check.
A practical setup
One r/opencodeCLI user reported that Step 3.7 Flash handled image descriptions well, while a commenter in the StepFun thread said its tool calling felt unreliable. Those are individual, non-browser tests, so treat them as reasons to validate your own client workflow, not as model performance proof. Read the first report and the tool-calling discussion. The official model card and provider listing are the right places to check weights, license, and current serving options. An API endpoint may support tool calls, but the browser client must still expose those tools and be able to run them locally.
For setup, see the Tabbit CLI guide, the existing-browser connection guide, the first-task checklist, and the CLI versus MCP guide. The Codex setup example and login reuse guide cover adjacent setup details. Use the browser prompt template to make stop conditions explicit. If an action is unavailable, use the click troubleshooting guide. For model-side reasoning background, see agentic reasoning in LLMs.
First confirm the account and target record in Tabbit Browser. In a compatible local client, discover the installed Tabbit skill. Clients with named skill commands may use /tabbit; Pi uses /skill:tabbit; some clients expose /skills. Skill discovery, launcher reachability, model selection, and site login are separate checks. Run the installed tabbit-cli diagnose, then start a uniquely named task. The CLI operates in the Tabbit environment, where a task can use the existing signed-in session. A separate task tab lets you keep browsing while it works. This reuse was checked with a local test fixture, not with this model/client combination.
Draft a named review
The StepFun API platform and OpenRouter list current serving options; availability can change. The open Hugging Face weights do not imply that every local client includes a ready-made browser workflow.
FAQ
Is Step 3.7 Flash open weight?
The Hugging Face model card lists the weights under Apache-2.0. Hosting the weights yourself still requires suitable hardware and a compatible inference runtime.
Is Step 3.7 Flash the same as Step 5 Preview?
No. They are separate releases with separate model IDs and routes. Verify the exact entry in your provider before a run.
Can it use a signed-in browser by itself?
No. A model endpoint does not provide a browser session. A compatible local agent and a browser connector such as Tabbit CLI are separate parts of the setup.
How do I check whether my client offers it?
Open the client’s model selector and confirm the provider and exact model ID. If it is absent, select another supported model or stop; do not assume an alias is equivalent.
Can I run it locally?
The weights are published, but a large model needs substantial compute and a compatible runtime. Check the model card and your hardware before downloading.
What should the agent do first?
Use a read-only task with a stable record ID, cite each source page, and save a named review draft. Verify the results yourself before any site change.