OSWork
AI as a work system

From zero to your agent workspace, command by command: Windows terminal, a projects folder, Codex or Claude Code, GitHub with an SSH key and a VPS. Once you can navigate Windows, you navigate the VPS the same way.

Command by command · copy and paste

OSWork in practice

Follow the order on a Windows 10 or 11 computer. Each step shows the command and what you should see on screen. Wherever you see YourName or YOUR-USER, use your own.

Part 1 — Your computer

The terminal is just another window onto the same Windows folders. Here you see it with your own eyes.

  1. Step 1

    Open the terminal

    Press the Windows key, type cmd and press Enter.

    You see: A black window showing C:\Users\YourName> — that is your personal folder.

  2. Step 2

    Create the projects folder and your first project

    Type one command at a time and press Enter after each.

    cd %USERPROFILE%
    mkdir projects
    cd projects
    mkdir my-site
    cd my-site

    You see: C:\Users\YourName\projects\my-site>

  3. Step 3

    See in Windows where everything lives

    This is the most important step. The command below opens File Explorer exactly in the folder the terminal is in.

    explorer .

    You see: The my-site folder open in File Explorer, inside projects. Terminal and Explorer show the same place: what you create in one appears in the other.

  4. Step 4

    Navigate with 6 commands

    That is all you need to move around. Practice: go up one folder, list and go back in.

    dirlists what is in the folder
    cd nameenters the folder
    cd ..goes up one folder
    mkdir namecreates a folder
    explorer .opens the folder in Windows
    clsclears the screen
    cd ..
    dir
    cd my-site
  5. Step 5

    Install Git, GitHub CLI and Node (once)

    winget comes with Windows. After installing, close cmd and open it again so it sees the new programs.

    winget install --id Git.Git -e
    winget install --id GitHub.cli -e
    winget install --id OpenJS.NodeJS.LTS -e

    You see: After reopening: git --version and gh --version print a version number.

  6. Step 6

    Install the agent: Claude Code or Codex

    Choose one, or both. The first time you open it, sign in with your subscription (Claude Pro/Max or ChatGPT Plus/Pro).

    curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
    npm install -g @openai/codex

    You see: The first line installs Claude Code; the second, Codex. In a new window: claude --version or codex --version.

  7. Step 7

    Work inside the project folder

    The agent only sees the folder you are in. Enter it and start the agent (claude or codex). Ask: “Create an index.html with a simple page about me and an AGENTS.md file with the rules for this project.” Type /exit to leave.

    cd %USERPROFILE%\projects\my-site
    claude
    dir
    start index.html

    You see: The new files appear in dir and in File Explorer; start opens the page in your browser.

Part 2 — GitHub: save and publish

git keeps versions of the project, gh talks to your GitHub account and the SSH key is your password-free identity.

  1. Step 8

    Tell Git who you are

    Use the same email as your GitHub account.

    git config --global user.name "Your Name"
    git config --global user.email "you@email.com"
  2. Step 9

    Create your SSH key

    Press Enter at the 3 questions. Then open the folder where the key was saved.

    ssh-keygen -t ed25519 -C "you@email.com"
    explorer %USERPROFILE%\.ssh

    You see: id_ed25519 is the private key: never send it to anyone. id_ed25519.pub is the public one: that is what you give to GitHub and to the VPS.

  3. Step 10

    Connect gh to your account and upload the key

    Answer: GitHub.com → SSH → choose id_ed25519.pub → Login with a web browser. Then test the key (answer yes the first time).

    gh auth login
    ssh -T git@github.com

    You see: Hi YOUR-USER! You've successfully authenticated.

  4. Step 11

    Create the repository and push the project

    Public: anyone can see it. Private: only you and the people you invite. For private, replace --public with --private.

    cd %USERPROFILE%\projects\my-site
    git init
    git add .
    git commit -m "first version"
    git branch -M main
    gh repo create my-site --public --source=. --push

    You see: The address github.com/YOUR-USER/my-site with your files.

  5. Step 12

    Publish the page on GitHub Pages

    Free on public repositories. You can also do it on the website: Settings → Pages → branch main.

    gh api repos/{owner}/{repo}/pages -X POST -f "source[branch]=main" -f "source[path]=/"

    You see: In 1 or 2 minutes the page opens at https://YOUR-USER.github.io/my-site/

  6. Step 13

    The everyday routine

    Changed something? Save a version and push it. Or ask the agent: “save and push to GitHub”.

    git add .
    git commit -m "what changed"
    git push

Part 3 — VPS: the same, on a server

A VPS is a Linux computer that stays on 24 hours a day. You enter it from the same terminal and navigate the same way; only a few names change.

  1. Step 14

    Rent the VPS with your key

    Choose Ubuntu. When creating it, the provider asks for an SSH key: paste the text this command prints.

    type %USERPROFILE%\.ssh\id_ed25519.pub

    You see: One line starting with ssh-ed25519. Copy the whole line.

  2. Step 15

    Enter the VPS

    Replace VPS-IP with the number your provider shows. Answer yes the first time. Type exit to leave.

    ssh root@VPS-IP

    You see: root@vps-name:~# — the terminal is now the server.

  3. Step 16

    Same navigation, different names

    There is no File Explorer on the VPS: ls does that job.

    dirls
    cd name / cd ..cd name / cd ..
    mkdir namemkdir name
    clsclear
    type filecat file
    %USERPROFILE%~
    mkdir -p ~/projects
    cd ~/projects
    ls
  4. Step 17

    Bring the project and install the agent

    A public repository clones directly. If it is private, install gh (apt install -y gh) and run gh auth login, as on Windows.

    apt update && apt install -y git
    git clone https://github.com/YOUR-USER/my-site.git
    cd my-site
    ls
    curl -fsSL https://claude.ai/install.sh | bash

    You see: The same files as on your Windows, now on the VPS. Run claude inside the folder, as in step 7.

Part 4 — When you want to connect other systems

VercelImports the GitHub repository and publishes the site on every git push, with your own domain. Good for sites and apps that will grow.
SupabaseDatabase, user login and file storage for your app. The agent writes the integration; you keep the keys out of the repository.

Want to go deeper? Choose the course

The step-by-step above is the path. The courses explain each part calmly.

All editions ↓

Choose your OSWork edition

Two paths to organize your work with AI. Choose by your experience and the time you have. The previous editions are at the end of the page.

OSWork v6.2 — the full path, step by step

The complete v2 path rebuilt for beginners: eight modules and 49 lessons of about 15 minutes. From chat to the terminal and Codex, folders, Skills, Git, a Telegram bot and a VPS, with visual step-by-steps and a glossary of technical terms.

OSWork Quick — hands-on

The 25 steps on this page as a course: cmd and folders on Windows, File Explorer, Claude Code or Codex, Git with gh and an SSH key, GitHub Pages and a VPS. Four parts, with progress, notes and a command cheat sheet.

The step by step on video, with Nei

The 17 steps on this page done command by command, copy and paste: from an empty terminal on Windows to the site published on GitHub Pages and the same project running on a VPS, with the agent working inside the folder. Nei’s avatar and voice, 8 minutes, in Portuguese, SRT subtitles.

Videos of the previous Quick edition

The first Quick edition (organizing work with AI, no terminal) in seven lessons, with Nei’s avatar and voice, illustrations and SRT subtitles.

Advanced

The technical v2 path, module by module

Expand each module to see its six topics. Links open the full course in the language of this page.

Module 1 — Models: choose by task

Compare models with a real task and a quality criterion.

  1. AI as a work system
  2. Kinds of AI and what they are for
  3. Model is not reasoning effort
  4. Create a quality rubric
  5. Understand access and billing
  6. Define the autonomy
Open the full module
Module 2 — Chat, Work and Desktop

Write a work order with inputs, output, and review.

  1. Chat resolves a conversation
  2. Work receives an order
  3. Desktop brings the files closer
  4. Local and cloud are execution choices
  5. Write a delivery contract
  6. Review the received work
Open the full module
Module 3 — Terminal and Codex in practice

Open a training project in Codex and produce a verifiable change.

  1. Terminal is an entry point
  2. Install from the official source
  3. Authenticate without spreading secrets
  4. Enter the folder before requesting
  5. Do a first reading task
  6. Use permissions and recovery
Open the full module
Module 4 — Folders, Markdown and secrets

Build the digital house and separate knowledge from credentials.

  1. A folder represents a context
  2. Markdown is organized text
  3. Each file has a job
  4. Secrets are not shareable knowledge.
  5. Ignore before the first commit.
  6. Do a context cleanup.
Open the full module
Module 5 — AGENTS, Skills and memory

Create project instructions and a reusable capability with a review criterion.

  1. AGENTS.md guides execution
  2. Global and project complement each other
  3. Skills package procedures
  4. Memory needs maintenance
  5. Failures become small protections
  6. Test reusable capability
Open the full module
Module 6 — Git and GitHub without losing work

Save a version, inspect differences and recover a training change.

  1. Git is the project's history
  2. Observe before staging
  3. Save a version with intent
  4. Clone and update carefully
  5. Recover without deleting history
  6. Publish only what you reviewed
Open the full module
Module 7 — Telegram as work interface

Run a restricted query bot and understand where AI comes in.

  1. Telegram is the interface, not the agent
  2. Create the bot and protect the token
  3. Authorize people and actions
  4. Start with long polling
  5. Connect capabilities in stages
  6. Test operation and failures
Open the full module
Module 8 — VPS from scratch and 24/7 operation

Prepare a deployment plan, monitoring, backup and service verification.

  1. A VPS is a machine under your responsibility
  2. Enter via SSH and preserve access
  3. Install only what is necessary
  4. Protect the network and credentials
  5. Systemd supervises the process
  6. Availability requires a care routine
Open the full module

Advanced

Kit for the technical path

The kit includes templates for AGENTS.md, memory, decisions, failure records, task contracts, a report Skill and a VPS plan. It includes a Python bot with an offline self-test.

The training bot is deterministic: it does not call an AI model or execute messages as commands. AI integration is explained as a later step.

Previous versions

OSWork v6.2 rebuilt the complete v2 path for beginners. The previous editions remain open for anyone who started with them.

Previous version · PT · EN · ES

OSWork v2 — technical path

Eight modules, four tracks and 48 topics. From chat to the terminal and Codex, files, Skills, Git, a Telegram bot and supervised VPS operation. Includes a practice kit.

Previous version · PT · EN · ES

OSWork v6 — beginners, visual

For people just starting out: seven lessons of about 15 minutes with simulated chat screens, real before-and-after examples and visual step-by-steps. Build folders per topic, a sheet with your rules, a request template and a checking routine, with nothing to set up.

Previous version · PT · EN · ES

OSWork v5 — for beginners

For professionals aged 40+ with little AI experience. Seven lessons of 20–25 minutes to organize folders, instructions, reusable requests and a review routine, without programming.