Documentation
DocsGetting started

Quickstart

Start coding with AppJet in minutes

1. Connect GitHub and open a repository

Open AppJet and sign in with GitHub. Authorize the GitHub App for the repositories you want to use, then select an existing repository or create a new one from the repository list.

AppJet uses an appjet working branch. When you open an existing project for the first time, this branch is created from the repository’s default branch. Check the selected repository and branch before starting work.

Use the file explorer to inspect your code or edit a file manually. See GitHub and branches for the complete workflow.

2. Give the agent a clear task

Describe the outcome, the relevant behavior, and how you will know the task is complete. For a new project, try:

Build a responsive Hello World page with a light and dark theme. Verify that the project builds successfully.

For an existing project, start with a specific bug or feature. Include the exact error and reproduction steps when something is broken. Follow the plan and activity, and inspect the checks before treating the task as complete.

3. Build and deploy

Ask the agent to build and deploy the app, or use the deployment control in the workspace. After a successful deployment, open Preview or the deployment URL in Settings → Overview.

Deploying on AppJet is optional. You can review and merge the GitHub changes or deploy them elsewhere.

Configure the app

  • Network: check the exposed port and enable WebSocket support if your app needs it.
  • Environment variables: configure secrets and runtime settings outside your source code.
  • Virtual disks: add persistent local storage on Starter or Pro.
  • Supabase: connect a database, authentication, object storage, or Edge Functions.
  • Logs: inspect runtime errors separately from build failures.
  • History: review changes, commits, and builds.

The agent can help with supported actions. If a tool, permission, or integration is missing, it should explain the blocker and what you need to do next. See configuration.