OSWork is the step that separates people who use AI from people who create with it. You'll learn six terminal commands, organize your work in folders with markdown text files, and write an AGENTS.md with the project rules. Then you start the agent inside the folder, give it a task, and check the result. Finally, you add a safety net: Git to undo mistakes and a secrets file for your keys.
Sequence 1 — From chat to the terminal: OSWork
In chat, you become the messenger
Chat AI can't see your files and forgets what you explained yesterday.
Every answer has to be copied and pasted into the right place. You spend the day carrying text from the window to your work and back. OSWork shows the path through three windows, Chat, Work, and Desktop, and then the terminal, where the agent lives.
The terminal is just another window
You type a command and it responds. This isn't programming: it's moving through your folders without a mouse.
| What you want | Windows (cmd) | Mac and Linux |
|---|---|---|
| See where you are | cd | pwd |
| List the folder | dir | ls |
| Enter a folder | cd projetos | cd projetos |
| Go up one folder | cd .. | cd .. |
| Create a folder | mkdir meu-projeto | mkdir meu-projeto |
| View a file | type AGENTS.md | cat AGENTS.md |
# Mac and Linux: your agent's first folder
mkdir -p projetos/meu-primeiro-agente
cd projetos/meu-primeiro-agente
pwd
lsOne folder per project, one AGENTS.md
Folders are the key. Inside each one, you'll find markdown text files.
The AGENTS.md contains the project rules: who you are, what the agent can do, and what it can't. The agent reads this file every time it starts. It's like handing a new employee the manual.
# Who I am Ana, an accountant who works with small businesses. # Rules for this project - Write in Portuguese, using short sentences. - Don't delete files without asking. - Before you finish, say what changed and how I can check it. # What's here - index.html: my page
You give the task, the agent does it
Go into the project folder and start Claude Code (claude) or Codex (codex).
cd projetos/meu-primeiro-agente
claude # or: codexRead AGENTS.md. Create an index.html with a simple page about me, using what's in it.
The files appear in the folder. Open the page in your browser, ask for a correction, and check it again. You didn't program anything: you gave the task, checked the result, and made a decision. That's management.
The safety net: Git, secrets, and VPS
Mistakes are cheap when you can roll them back.
Git saves every version
Make a commit before each big change. If the agent makes a mistake, git restore brings the file back.
Keep secrets out of text
Keys and passwords go in a .env file, listed in .gitignore. Never put them in the code.
Telegram and VPS
At the end of the journey, Telegram becomes the interface and a VPS keeps the agent running while your computer is off.
git init
git add .
git commit -m "primeira versão"
# don't like the agent's change?
git restore index.htmlExercises in this sequence
Do them in order. Each exercise has a "ready when" criterion: move on only when it is true.
- E1
Your first folder in the terminal · 10 min
Ready when: you can reach the folder using only the terminal and say which folder you're in.
- E2
The employee manual: AGENTS.md · 15 min
Ready when: the file exists and has at least three rules you wrote.
- E3
The first task · 15 min
Ready when: the page opens in your browser and you've asked the agent for at least one correction.
- E4
The safety net: Git · 20 min
Ready when: you undid an agent's change with one command, without panicking.
- E5
Keep secrets out of text · 10 min
Ready when: git status doesn't show .env.
- E6
The agent reads your files · 20 min
Ready when: you found at least two of the sentences quoted in the summary in the original.
Courses, projects, and guides
Everything is open and free. Start with the first item on the list.
Open the terminal today
This is the step that unlocks Jarvis, queues, and automated social media. Create your first folder and give your agent its first task.
Open OSWork Quick →