Developer
documentation
Rogue's project formats, build and runtime lifecycle, publication, code export, authentication boundaries, and agent integration.
On this page
Connect your editor to the docs. Search a reference, retrieve its Markdown, and keep the source beside your code.
curl -fsSL \
https://rogueon.ai/docs/getting-started/markdownBuild with context.
TECHNICAL GUIDESProduct scope
Rogue is a hosted environment for generating and revising web artifacts through structured requests. This documentation covers the resulting project, its build and runtime dependencies, versioned previews, publication, and export. It distinguishes capabilities of the web workspace from services used by a generated application.
Technical referenceRequest, artifact, and release
- Specify the output, data contract, invariants, dependencies, and acceptance criteria.
- Follow the request state and inspect the saved artifact and preview. A request being accepted is not a completed build.
- Validate behavior and authorization, then publish the selected version. Subsequent edits remain in preview until another publication.
Specifications and context
Use bounded specifications with explicit inputs, state transitions, expected failures, and non-goals. Provide reference files or URLs with their intended role. Keep fixtures separate from production data and declare whether the project needs persistent storage, user identity, or external services.
Technical referenceWorkspace and artifact formats
Sites is the web-project workflow; Chat and Slides have separate roles. The generic app entry can open Chat. Within Sites, a saved result can be direct HTML or a Vite project. Vite can bundle HTML/TypeScript, a React island, or a React application: inspect package.json, entry points, and imports instead of assuming one framework.
Source ownership and portability
Generated code is yours; Rogue itself is not open source. The code viewer exposes saved files for inspection and copying. When available, GitHub export delivers an HTML or Vite project according to that version's artifact format.
Code export does not transfer database records, user identities, provider credentials, or hosted service routing. Establish the destination's build and runtime configuration and validate it before moving users. Review generated README content and Git history before changing repository visibility.
Technical referencePublication boundaries
Publish selects which reviewed artifact is served at the managed site address, with hosting included. Publishing a site, committing code to GitHub, and changing backend data are separate operations. Validate the destination rather than inferring its state from a successful preview.
A site's Rogue address (on p.rogueon.ai) uses X-Robots-Tag: noindex. You can share its public link, but that address is not intended to appear in search. For search discovery, connect a domain you own in the Publish panel: once the domain is verified, the site on it can be indexed. noindex does not make a public page private.
You can connect a domain you already own in the Publish panel; Rogue does not sell domains. Web output runs in a browser; Rogue does not generate .apk or .ipa packages or publish native apps to the App Store or Play Store.
Technical referenceAvailability and capacity
Rogue is in free beta with session and weekly usage limits. Free is the plan in use; Go and Max are listed below with their prices and are not on sale yet. Account usage, request context limits, and external-provider quotas are distinct constraints.
- Free: $0/month.
- Go: $10/month (coming soon).
- Max 5x: $50/month (coming soon).
- Max 25x: $200/month (coming soon).
Runtime and agent integration
Distinguish account connectors, generated-app dependencies, and agent access to documentation. A catalogue entry does not establish a connected account. Frontend export does not supply hosted authentication or credential proxies. Validate the actual connection, permissions, origin behavior, and provider response.
Public guides are available as canonical HTML and equivalent Markdown. Use the agent integration reference for discovery and supported documentation interfaces; reading product documentation does not authorize actions on private projects.
Technical referenceDiagnostics and references
For a defect, include the tested version, environment, minimal reproduction, expected and actual result, and sanitized network or console evidence. Identify whether it occurs in the preview, published site, or exported project.
Technical reference