PATH 02 / OSWORK

Environment

Turn folders into a reliable workspace.

0% 0 of 0

Read, apply to a small task and check the result before moving on.

2 modules

12 topics

75 min with practice

Guided step by step

Track map

2.1 ~40 min

🧭 Terminal and Codex in practice

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

2.2 ~35 min

🧭 Folders, Markdown and secrets

Build the digital house and separate knowledge from credentials.

Detailed content

MODULE 2.1

Terminal and Codex in practice

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

0% 0 of 0

What it is

The terminal is the window where you write commands for the computer. The shell is the program that interprets those commands. Here the terminal examples use Bash on Linux or macOS; on Windows, use a Bash environment via WSL or follow the official installer for Windows. Do not paste Linux commands directly into PowerShell without adaptation.

Why learn

Knowing which environment you are in avoids errors that seem like AI failures. The cd command changes the current folder; pwd shows the location in Bash. You do not need to memorize dozens of commands to get started.

Key concepts

Terminal; shell; current folder; command and response.

What it is

The official Codex page offers installers for macOS/Linux and specific guidance for Windows. Installing means adding the program to the machine. The installation command downloads and runs an official script; read the source, check the domain and use your own account. Do not run commands received from unknown pages.

Why learn

Installation, login and execution are different steps. A program that is installed still needs authentication. A completed login does not mean you opened the correct folder.

Key concepts

Official source; installation; version; diagnostics.

What it is

Run codex login and complete the browser flow to sign in with ChatGPT. If you choose the API, the key must be in the OPENAI_API_KEY variable; pipe it via standard input, without typing it in the command. A .env file alone does not authenticate Codex: some mechanism must load the variable.

Why learn

Pasting the key in examples, messages, or history can expose the account. It is also possible to be authenticated by the wrong method and consume a different modality than expected.

Key concepts

codex login; codex login status; standard input; active account.

What it is

The working folder is the task bench. Create a small area with training files before allowing changes. A README.md describes the purpose for people; AGENTS.md gives operational instructions to the agent. You do not need to open your entire personal folder to experiment.

Why learn

A small scope reduces ambiguity and makes reviewing differences easier. When something goes wrong, it is clear which files should have been affected.

Key concepts

Local scope; README; AGENTS; input files.

What it is

Start by requesting inspection: list the structure, read instructions and explain pending items. Ask the agent to cite which files it used. After checking, authorize a small, named change, such as creating plano.md with three next steps.

Why learn

Separating diagnosis and change creates a reference for review. You learn the flow without mixing installation, large refactoring, and publishing in a single attempt.

Key concepts

Inspect; plan; change; validate.

What it is

The client’s permissions control access to files, network, and execution. Natural‑language instructions guide behavior, but they do not replace technical isolation. Start with permissions restricted to the training folder. Do not teach removing all protections to work around any error.

Why learn

Recovering a change requires knowing what existed before. Git and file copies provide rollback points; they will be practiced later. Read what the command will do before expanding permissions.

Key concepts

Minimum permission; small changes; comparison; rollback point.

View full →

MODULE 2.2

Folders, Markdown and secrets

Build the digital house and separate knowledge from credentials.

0% 0 of 0

What it is

The ~ symbol represents the home folder in Bash. Inside it, projects gathers independent work. Use clear names and avoid mixing documents from different clients. The config folder stores cross‑cutting knowledge; each project keeps its own inputs and results.

Why learn

Separate contexts help limit what the AI needs to read. A folder full of unrelated topics adds noise and makes it hard to explain where a conclusion came from.

Key concepts

Personal folder; projects; context; inputs and outputs.

What it is

Markdown uses simple symbols to organize text: # creates a title, ## creates a subtitle and a hyphen starts a list item. The file remains plain text, readable even without a special editor. The name ends with .md. You do not need to write code to record clear instructions.

Why learn

Small, named, easy‑to‑edit files last longer than a lost conversation. They can be reviewed by people and consulted by agents. The value comes from clarity, not elaborate formatting.

Key concepts

Title; list; code block; link; plain text.

What it is

memoria.md records stable preferences; decisoes.md explains choices; dicas.md stores useful procedures; falhas.md documents problems and fixes. Do not put everything in one giant document. When a decision changes, record the date and reason so you don’t keep contradictory rules.

Why learn

Separating functions makes it easier to consult only what’s needed. A failure history should not become a list of mandatory commands in every task. Queryable knowledge and permanent instructions are different things.

Key concepts

Selective memory; dated decisions; procedure; history.

What it is

A .env file can store variables such as TELEGRAM_BOT_TOKEN or DATABASE_URL. It is not encrypted: anyone with access to the file can read it. Use appropriate permissions and never include real values in screenshots, course examples, or files sent to the AI without necessity.

Why learn

Credentials allow actions on behalf of an account. Separating the .env.example model, without real values, from the local .env lets you share the structure without distributing access.

Key concepts

Variable; secret; .env.example; runtime reading.

What it is

The .gitignore lists files that Git should ignore when they are not yet tracked. Include .env, private variants, and temporary folders. Keep an explicit exception for .env.example. Before committing a version, examine git status and the staged files.

Why learn

Ignoring later does not erase a secret from history. If the key leaked, the first fix is to revoke or rotate it at the source; deleting the line from the file does not invalidate a copy already seen.

Key concepts

Tracked files; exclusion patterns; change review; revocation.

What it is

The AI does not automatically read every existing Markdown file on the computer. Specify which documents to consult and keep references in AGENTS.md when needed. Before a task, remove irrelevant data from the working copy and update expired decisions.

Why learn

Useful memory needs to be findable and correct. An old file can be more harmful than no memory if it contains a service address or process that has already changed.

Key concepts

Context selection; date; source of truth; periodic review.

View full →