The complete Entry Agents guide for new vibe coders.

Entry is a place where you describe software and an AI coding agent helps create it. If you have never built software before, begin with a small idea such as a personal landing page, a habit tracker, a simple calculator, or a small business booking page.

1. Open Sign in and choose one of the available sign-in providers.
2. After signing in, use Get Started if Entry shows the setup flow. Complete the account step. GitHub is optional, so do not connect it unless you want repository features.
3. Open Sessions and create a new session. Choose a blank Workspace when you are starting a new idea.
4. Give the agent a small first request. Do not ask for a huge company-sized product in one message. Ask for a foundation, inspect it, then add the next feature.
5. Keep the session open while Entry creates files, runs commands, and explains its work. Read the result before asking for the next change.

A Workspace is the working environment for the session. It is where the project files, commands, builds, tests, and previews live. You can start empty, upload files, or connect an existing repository later.

You do not need special prompt words. Tell Entry what you are making, who it is for, what it should look like, and how you will know it works. Ask it to explain unfamiliar words instead of pretending you understand them.

First project: a simple website

I am new to coding. Build a simple one-page website for a small Lagos bakery called Sunrise Bakes.
Use a warm, friendly style. Include a hero section, menu cards, opening hours, location, WhatsApp contact button, and a mobile layout.
Start by inspecting the blank Workspace, explain the files you create in simple language, then run the available checks.

First project: a useful personal tool

Build a simple expense tracker for someone who is new to coding.
I need to add an expense, choose a category, see the total for this month, and delete an entry.
Use a clean mobile-first interface. Keep the first version small. After building it, tell me how each main file works and test the add, total, and delete flows.

Ask for a change

The page looks good, but the main button is hard to notice on a phone.
Make the button clearer, improve spacing on small screens, and do not change the colors of the rest of the page.
Show me what you changed and check that the layout still works on desktop and mobile.

Ask for an explanation

Explain this project like I have never coded before.
Tell me what the entry point is, where the page layout lives, where the data is stored, and what command checks whether the project works.
Do not change any files while explaining.

Ask for debugging help

The app shows a blank screen after I click the Save button.
Please reproduce the problem, inspect the browser and server errors, find the smallest safe fix, test the fix, and explain the cause in beginner-friendly language.

A useful prompt pattern

Context: what you are building. Task: what should change. Limits: what must not change. Proof: how Entry should test or demonstrate success.

Settings pages

Once a session opens, think of the screen as a project control room. The chat is where you speak to the agent. The surrounding panels help you inspect the result.

Use the live pricing page for current plan names, prices, limits, and payment details. This guide explains the flow without hard-coding numbers that may change.

1. You sign in and have an account with a plan or available credit balance.
2. You choose a model for a session, or use the model default provided by Entry.
3. You send a request. The request includes your conversation and the context needed for the agent’s next step.
4. The selected model processes the request. Longer context, more output, tool-heavy work, and more complex tasks can use more credits.
5. Entry records the usage and updates the balance through its normal billing path. The Usage area is where you review activity.
6. When your balance or plan limit is low, choose a suitable model, shorten unnecessary context, wait for a reset where applicable, or use the billing page to manage your plan.

There is no separate Workspace or sandbox charge. Credits pay for model usage, and the live pricing page is the source of truth for current plan prices and limits.

What happens from plan to renewal

1. Start on Free with a one-time $1 credit and access to the Free model. No card is required for the trial.
2. Choose a paid plan when you need more credit or access to all models. Plus is $5/month for $10 credit, Entry is $13/month for $50 credit, Pro is $20/month for $100 credit, and Max is $40/month for $180 credit.
3. Complete checkout. Your plan becomes active and its included credit is added to your balance.
4. Each model request spends credit based on the model and the work involved. Longer conversations, larger answers, and tool-heavy tasks normally use more.
5. Check the remaining balance and usage in Pricing or Settings → Usage. A top-up can add separate pay-as-you-go credit when that option is available.
6. At the next successful monthly renewal, the plan charge is made and that plan’s included credit is added again. Existing balance is not silently replaced by the renewal grant.
7. Entry has extra rolling usage windows: $10 over five hours, $25 over seven days, and $50 over 30 days. These refill continuously as older usage leaves each window.
8. If you cancel, checkout fails, or the balance is too low, review the billing page before starting expensive work. The plan page always shows the current prices and availability.

You can learn vibe coding without GitHub. A blank Workspace is the best starting point for a new creator. Add uploaded files when you already have material to inspect. Connect GitHub when you want to work with a repository, branch, commits, diffs, or pull requests.

1. Start with a blank Workspace if you have only an idea.
2. Upload files if the project exists on your computer but is not in GitHub.
3. Connect GitHub during onboarding or from Connections when the repository already exists.
4. Choose the repository and branch carefully. Ask Entry to inspect before making broad changes.
5. Review the diff, run checks, and decide whether to commit or create a pull request.

Agent

The AI worker that plans and performs a task.

Vibe coding

Building by describing intent in natural language, reviewing results, and iterating with an AI coding tool.

Session

A project-level workspace and its conversations.

Chat

The conversation where you give the agent instructions and receive results.

Workspace

The private working environment containing files, commands, builds, and tests.

Model

The AI system selected to process a request.

Credits

The usage balance applied to model requests.

Diff

A view showing added, removed, and changed lines.

Branch

A separate line of Git work used to isolate changes.

Commit

A saved checkpoint of changes in Git.

Pull request

A request for changes from one Git branch to be reviewed and merged into another.