Real book club workflow
All eleven new lessons in order. The optional Chrome profile guide is available separately.
Before you start: Install Orbit and sign in. Use the starter project linked below. Each chapter gives its additional prerequisites. Private account authorization is completed by you.
Recorded by operating the real Orbit application with a real backend and provider responses. Tutorial project data is separate from customer work. Email addresses and unrelated history are hidden. Narration is added; pauses may be held and long waits removed. AI results and available models can differ. The account setup stops before private sign-in. The remote chapter uses a desktop browser. Agent and routine chapters require the prepared runner fixes.
Follow along
- Set up a book club workspace — Select the project
We will prepare a book club meeting page. Extract the starter project linked below, then add that folder to Orbit. Open the navigation menu and select Orbit Tutorial Project. The eye button shows the folder path.
- Set up a book club workspace — Create a workspace
In Code, select plus Workspace. Choose your project and name this workspace Meeting page review. Save it. A workspace groups your terminals. It does not create a second copy of the project folder.
- Set up a book club workspace — Check the saved workspace
Open Settings, then return to Code. Meeting page review is still selected. You now have a separate place for this task. The next lesson will create a real checklist in the project.
- Install Codex inside Orbit — Open the installer
Open Settings, AI accounts, then Add other AI providers. This installs the provider program on your computer. For this example, Node.js and npm are already installed. Use the provider documentation linked below.
- Install Codex inside Orbit — Install the official program
Paste npm install dash g at openai slash codex. Select Install provider. Watch the terminal while the real package downloads. If npm is not recognised, install Node.js LTS, restart Orbit, and try again.
npm install -g @openai/codex - Install Codex inside Orbit — Verify installation
The command reports that two packages were added. Orbit shows ChatGPT slash Codex as Installed. Installation is complete. Use Add account next if you have not signed in. Installing the program does not include a provider subscription.
- Choose an account for project work — Check existing accounts
Open Settings and AI accounts. Refresh the list to detect existing sign-ins. This recording uses a real saved Codex account. The email address is hidden. A saved login can still be blocked by provider limits, so test it with a small task.
- Choose an account for project work — Prepare another account
Select Add account beside Codex. Give it a clear name, such as Book club work. Keep Provider subscription selected for a subscription login. Open the correct Chrome profile, then select Next. API keys have separate usage charges.
- Choose an account for project work — Complete private sign-in yourself
For a new account: continue to the provider, confirm the intended identity, finish sign-in, return to Orbit and Refresh accounts.
This take does not complete a new login. It uses an existing signed-in account for the recorded work.
- Create a meeting checklist — Open a project session
In Code, select New terminal. Choose your saved Codex account, a model you can use, and its effort setting. This take uses GPT 5.6 Sol with low effort. Open the terminal. If the provider asks whether you trust the folder, review the path before confirming.
- Create a meeting checklist — Give a specific task
Click inside the terminal. Ask it to read the project brief and create meeting checklist dot m d with three checks. Press Enter. This is a real provider request. Wait for its response. Your wording and model may produce a different checklist.
Read README.md. Create meeting-checklist.md with three checks for our book club meeting: date/time/place, organiser contact, and phone readability. Stay inside this folder. Do not browse or publish. - Create a meeting checklist — Review the result
The provider reports the file it created. You can change the pane layout to work side by side. To verify the result, open Settings, Project files, then meeting checklist dot m d. Read the actual three checks. Do not rely only on the completion message.
- Save and use a book club reviewer — Create the reviewer
Agent instructions: Review book club website information. Give three clear improvements. Stay in the current folder. Do not change files or publish anything.
Reference memory: We care about the next meeting details and a way to contact the organiser.
- Save and use a book club reviewer — Add a focused skill
Skill: Check the next meeting date, time and place. Check visible contact information. Check that the page is readable on a phone. Return three short improvements.
- Save and use a book club reviewer — Run the saved agent
Open the saved agent chat. Ask it to review meeting checklist dot m d using Phone readability. Choose the model and send the request. The real response recommends complete meeting details, clear contact links and readable mobile text. Review those suggestions before acting on them.
Read meeting-checklist.md. Apply your saved Phone readability skill and give three practical improvements. Do not change files. - Continue the saved review — Reopen saved work
Return to Agents, select Book club reviewer, and open its saved review conversation. The earlier request and answer appear again. Use that saved conversation to continue the same task. Other conversations are blurred for privacy.
- Continue the saved review — Ask the next question
Ask for one short next-action checklist. Send the follow-up and read the real response. It keeps the meeting details, contact links and mobile checks from the earlier discussion. You have continued saved work without starting the project explanation again.
Turn your three improvements into one short next-action checklist. Do not modify files. - Connect Context7 documentation — Find the plugin
Open Settings and Plugins. Search for Context7. In this use case, we want a documentation connection for later development work. Open the result and read the service details before adding it.
- Connect Context7 documentation — Connect the service
Add the plugin, then select its connection action. Orbit contacts the real service. Wait for the result. The recording shows Connected. If your service requires a key or sign-in, complete its official setup before checking again.
- Connect Context7 documentation — Verify the saved connection
Close the details and check the Connected status in the list. The connection is now saved. Use a new supported agent session when you need the tool. This lesson proves the connection; it does not claim that an AI has already used its tools.
- Schedule a real checklist review — Define the scheduled task
Open Settings, Routines, then New routine. Name it Meeting checklist, one-time review. Select the project and your Codex account. Ask it to read the checklist and save routine review dot m d. Set a three-minute time limit.
Read meeting-checklist.md. Write routine-review.md with three short checks for the meeting information. Only write in this project. Do not browse or publish. Finish after saving the file. - Schedule a real checklist review — Set a future time
Use a future date/time in the displayed timezone, not the historical date shown in the recording.
Choose Once, enabled. Leave account switching off. Keep Orbit running and the PC awake and online.
- Schedule a real checklist review — Verify the completed run
Run history now shows Finished and the actual account used. A one-time routine has no further run scheduled. Open Settings, Project files, then routine review dot m d. The three checks are really saved in the folder. Review the file before you use it.
- Save and finish a project note — Write the next task
Open the menu, then Notes. Create a note called Check the meeting page on a phone. Set the category to Website launch and write what you want to check. The note stays with this project.
- Save and finish a project note — Save and reload
Select Save note, then Reload saved note. Check that the title and text remain. All changes saved confirms the operation. Notes record your plans; saving one does not send a prompt to an AI.
- Save and finish a project note — Find and update it
Search for meeting page. Open the matching note, change its status to Done, and save. Use this after you finish a real task. Here we demonstrate the status change on the tutorial note and verify that it stays saved.
- Read files and save notes in a browser — Connect to your computer
Sign into the Orbit website using the same account as the Windows app. Select your linked computer if asked. This is the live browser workspace, connected to the PC. Select the tutorial project and confirm Connected before you continue.
- Read files and save notes in a browser — Read the desktop output
Open Settings, then Project files. Select meeting checklist dot m d. The browser reads the real file that Codex created on the PC earlier. This recording uses the public website and its existing computer connection.
- Read files and save notes in a browser — Save a task from the browser
Open the menu and Notes. Create Confirm the meeting time. Add a category and your check, then save. Reload the saved note and confirm that the text remains. This gives you a next task on the same project when you return to the computer.
- Make Orbit easier to read — Adjust terminal text size
Open Settings and find Appearance and notifications. Move the Terminal text size slider. This changes terminal text, rather than the size of every label in the app. Choose a size that lets you read a full command comfortably.
- Make Orbit easier to read — Choose a theme
Turn on Light theme to see the difference, then choose the theme you prefer. This take returns to dark mode. Leave Settings and return. Your selected preferences are still shown.
Resources
More lessons
Published by Nexvia · Updated