ByeBuy.ai
BUILD YOUR ESCAPE ROUTE · ✦ CURSOR · HOST IT · ◫ SUPABASE · CONNECT IT · ↯ RELAY · BUILD YOUR ESCAPE ROUTE · ✦ CURSOR · HOST IT · ◫ SUPABASE · CONNECT IT · ↯ RELAY ·
← BYEBUY NOTES

September 11, 2026

YOUR FIRST AI CLI SESSION

A beginner opens a terminal in a project folder with a friendly AI guide.

Your first AI CLI session should not begin with “build my startup.” It should begin with orientation: open one safe project folder, start one agent, and learn what it sees before asking it to act.

The terminal is not a test of whether you are technical enough. It is the place where an AI agent can see the files, commands, and outputs that make up a real project.

Before you start

Choose a folder that is safe to inspect. Do not begin in a folder full of private credentials, irreplaceable documents, or a production system you do not understand.

Check these four things:

CheckWhy it matters
You are in the project rootThe agent can find instructions and surrounding files
Important files are savedYou do not confuse unfinished manual work with agent changes
You know whether the app is local or liveThe agent understands the environment and authority boundary
You have a Git checkpoint if the project mattersYou have a clear way to inspect or undo changes

The first request

Start the agent from the project root. Then give it this kind of request:

This is a better first session than immediately requesting a feature because it gives you a baseline. You can compare the agent's explanation with the actual folder. If it misunderstands something, correct the project documentation now.

Open project rootAsk agent to read and orientCompare explanation with real filesApprove one small planVerify result
Open project root → Ask agent to read and orientAsk agent to read and orient → Compare explanation with real filesCompare explanation with real files → Approve one small planApprove one small plan → Verify result

Understand permission before convenience

AI CLI tools may ask permission to read files, edit files, run a command, install a package, or connect to another service. Read the request before approving it.

RequestUsually reasonable?Pause when...
Read README.md or source filesYesThe folder contains secrets or private documents
Run local testsUsuallyYou do not recognize the command
Edit one named project fileOftenThe change is broad or outside the agreed task
Install a packageAfter reviewYou do not know why it is needed
Deploy or change cloud settingsOnly with explicit approvalAlways inspect scope, cost, and target environment

Do not turn off all approval prompts just to make the agent faster. Early prompts teach you what the agent is really doing.

The rhythm of one good session

1. Orient. Read context and map the project. 2. Plan. Ask the agent to state the files, approach, and checks. 3. Approve. Confirm the plan or tighten the scope. 4. Build. Let it make the focused change. 5. Verify. Run checks and use the browser yourself. 6. Record. Review the Git diff and update the handoff.

The agent may perform several commands inside the build step. That is fine. You should still be able to explain the larger loop afterward.

A safe first task

Ask the agent to create or improve a README.md. It can inspect the project and explain its purpose, install command, run command, test command, and folder structure. This is useful work, low risk, and immediately improves the next session.

Practical exercise

Open a project folder and run one orientation-only session. Save the agent's project map in a Markdown file. Then ask it to propose—not execute—the smallest improvement it could make. Practice saying “show me the plan first.”

Check your understanding

1. Why begin in the project root? 2. What should an agent do before changing an unfamiliar project? 3. Which actions deserve an explicit approval pause? 4. What is a low-risk first task for an AI CLI?

ARTICLE DISCUSSION

JOIN THE
CONVERSATION.

0 COMMENTS

BYEBUY ACCOUNT ACCESS

Sign in

Use your account to save routes and make the catalogue yours.

Enter your email and we’ll send a secure sign-in link and code.

NEW ROUTES ADDED WEEKLY · 9,235 CATALOGUE ENTRIES · BUILD · DEPLOY · QUERY · STACK · SAY BYE TO BUY · NEW ROUTES ADDED WEEKLY · 9,235 CATALOGUE ENTRIES · BUILD · DEPLOY · QUERY · STACK · SAY BYE TO BUY ·