AutoBE
    Preparing search index...

    Interface IAutoBeRunAutoViewOptions

    Options for IAutoBeAgent.runAutoView.

    AutoView produces a Next.js + shadcn/ui frontend on top of an SDK. Two sources are supported:

    • "interface" — the SDK from the most recent interfaceComplete event in this session. Requires the interface phase to have completed.
    • "shopping" — the bundled @samchon/shopping-api swagger as a stable reference. Lets the AutoView pipeline be exercised independently of the AutoBE pipeline.

    Samchon

    interface IAutoBeRunAutoViewOptions {
        backend?: { host: string } | null;
        designTheme?: string;
        runtimeAudit?: boolean;
        source?: "interface" | "shopping";
    }
    Index

    Properties

    backend? designTheme? runtimeAudit? source?

    Properties

    backend?: { host: string } | null

    Live backend the generated frontend should connect to.

    When backend.host is given the scaffold wires connection.ts with simulate: false so the dev server renders real data on first boot — the "user opens http://localhost:3000 and sees their actual catalog, not typia-random gibberish" promise the standalone CLI exists to deliver.

    Omit (or pass null) to fall back to simulator mode, which is only useful for swaggers that genuinely have no backend (AutoBE's interface phase, for example).

    Callers that already have a servers[0].url in their swagger should pass that here — extractBackendFromSwagger(payload) in @autobe/autoview is a small helper for exactly that.

    designTheme?: string

    Optional design-theme instruction passed to the product-plan and render phases verbatim. Examples:

    • "premium e-commerce, generous whitespace, rounded cards"
    • "enterprise admin, dense tables, monochrome palette"

    Leave empty for the default prototype-first look documented in frontend/CLAUDE.md.

    runtimeAudit?: boolean

    Opt into Phase 6 runtime audit: after typecheck the orchestrator boots next dev against the assembled tree, walks every screen with a headless Chromium, captures console / pageerror / navigation diagnostics, and feeds the broken pages back to the render phase for a single retry round. The retry pass closes the class of bugs tsc --noEmit cannot see — obj?.array.method(...) undefined-access patterns, missing client-only guards, react render crashes against simulator data.

    Defaults to false because the audit installs Playwright + Chromium (~150MB) and boots next dev once or twice per agent run, which adds ~10–20 minutes on top of the existing pipeline. Turn it on when polishing the generated frontend for a real user, or after the typecheck loop has driven errors close to zero and you want the runtime gate before shipping.

    source?: "interface" | "shopping"

    SDK source. Defaults to "interface".

    Settings

    Member Visibility

    On This Page

    Properties