oscode_Get started ↗
v0.19.0 · Web CLI, task management and live browser Read the guide ↗
THE FRONTEND WORKSPACE, IN YOUR TERMINAL

Build with your components.
Verify what users see_

An open-source AI CLI for frontend developers.
Reuse project components, check team rules,
and test real browser interactions.

REACT / VUE / ANGULAR / SVELTE / NEXT.JS / NUXT
npx @choijinwon/oscode@0.19.0 --agent frontend

Requires Node.js 22+. Start local commands without a model key.
Connect a model for AI code changes.

Installation and global setup →

Open model inspection with one click.

Inspect semiconductor classification, detection and polygon segmentation results in a workspace shaped by your model contract. Compare A/B results on the same image.

OSCODE Model Lab with inspection settings and two defect detection results
Actual Model Lab interface with synthetic inputs and sample results, not measured model performance. The current application UI is in Korean.
01

Open the workspace

Click 모델 검사 (Model inspection) beneath the terminal input. Narrow terminals show 검사.

02

Set up your models

Open an image and register A/B model contracts. Try synthetic samples without an API key.

03

Compare results

Review scores, bounding boxes and polygons. Adjust the display threshold or hide overlays.

04

Export evidence

Download comparison JSON with the image hash, model versions and original predictions.

Actual inference requires a separate model server. You can also import result JSON. A/B is a visual comparison, not an accuracy benchmark or automatic pass/fail decision.

Read the Model Lab guide →

Deliver results, with an approval trail.

Compose registered blocks with AI, run specialist workflows locally, and record quotes, deliverables and customer acceptance.

Local workflows available in npm 0.18.0. No online checkout, authenticated customer approval or automatic billing.
01

Quote

Agree on scope, output and price.

02

Execute

Run typed blocks with existing permissions.

03

Verify

Record output files and content hashes.

04

Accept

Record customer acceptance before invoice preparation.

Read the results-service guide →

Understand. Change. Verify.

01

Find existing components

Inspect the project catalog and identify reusable code.

/catalog →
02

Respect team rules

Check configured imports and code patterns before accepting changes.

/team-ui →
04

Share the evidence

Export passed, failed and unverified checks.

/evidence →

From everyday UI
to semiconductor screens.

Choose from 40 UI starters, including mobile, admin, ERP and 10 semiconductor components. Generate code and CSS for your framework.

Explore design commands →
LOCAL DATA EXPLORER

LOT → wafer → die

/design select next/semi-trace

Import JSON or CSV, validate coordinates and units, then inspect linked results and yield.

The other nine semiconductor starters use synthetic data. No MES connection, equipment control or automatic REST binding is included.

Data format and examples →

Route simple requests
without another model call.

OSCODE uses explicit local rules to prioritize relevant tools. Mixed or unmatched requests use the general route.

Transparent scope

This is a rule-based engine, not a trained classifier. It does not grant approval or guarantee token savings. Code generation still uses your configured model.

Configure local routing →

Before you start

Is OSCODE free?

OSCODE is MIT-licensed. Model usage or subscription costs depend on your provider.

Is the CLI fully available in English?

This release adds an English website and getting-started guide. Some CLI messages, generated UI labels and detailed guides remain in Korean.

Does a passing check mean production-ready?

No. It only covers the configured checks. Validate your application build, integration and business rules separately.

Data labeling · Office documents · Context diagnostics 0.18.0 ↗