PTENES
Skip to content
TRACK 2

🔌 Connect

With the map in hand, it’s time to connect. Have Claude call Codex through a command-line bridge, turn spreadsheets into MCP tools, point the bridge at your system, and use the browser with written rules.

4
Modules
24
Topics
~2h20
Duration
Practical
Level
0 of 240%
agent Claude Code 🤝 Codex · CLI 🔌 schedule · MCP 🏗️ ERP · CSV 🌐 site · browser

Learning path map

Detailed content

2.1~35 min

🤝 Claude uses Codex

Recipe R1: the codex-exec.sh bridge lets Claude ask Codex for a second opinion or a task without leaving Claude Code.

0 of 60%
What it is:

A kit script, runtime/pontes/codex-exec.sh, that wraps codex exec: sends a request to Codex and returns the response.

Why learn:

It’s the official route (CLI, level 3) for what mod videos did behind the scenes in the app.

Key concepts:

Bridge, CLI, codex exec, second opinion.

What it is:

Grant the script execute permission and ask Codex to respond only with PONG.

Why learn:

Testing the bridge outside the agent separates a bridge problem from a request problem.

Key concepts:

chmod +x, proof, PONG.

What it is:

The R1 prompt: Claude uses the bridge to have Codex review README.md, then compares that review with its own opinion.

Why learn:

Two different models make mistakes in different places; the comparison shows what one model alone would miss.

Key concepts:

Cross-review, read (N4), combine the answers.

What it is:

Pass the folder and workspace-write mode to Codex so it can create notas.txt with the word OK.

Why learn:

Changing files is N3: only when you ask, and the proof is that cat notas.txt shows OK.

Key concepts:

Sandbox, read-only, workspace-write, N3.

What it is:

The bridge only accepts read-only and workspace-write; requesting danger-full-access returns "sandbox rejected by POLITICA".

Why learn:

Seeing the refusal happen gives you confidence that the rule is in the code, not just on paper.

Key concepts:

POLITICA.md, refusal, exit code 2, per-action limit.

What it is:

The bridge variables (default model gpt-6-luna, default time of 600 seconds) and the “If something goes wrong” section of R1.

Why learn:

The bridge stopping, sandbox refusal, and blocked network each have a known cause and a one-line fix.

Key concepts:

Environment variable, timeout, stdin, LIMITES.md.

View Full
2.2~35 min

🔌 Your first MCP bridge

Recipe R3: a dependency-free MCP server turns Clara’s schedule and Sônia’s sales CSV into tools for the agent.

0 of 60%
What it is:

A standard way for a program to offer named tools and rules to any compatible agent.

Why learn:

The same bridge works with Claude Code and Codex: a local bridge (level 6) exposed through MCP (level 2).

Key concepts:

MCP, server, tool, stdio.

What it is:

listar_horarios_livres reads agenda.csv; resumo_vendas reads erp-vendas.csv and adds up by customer or product.

Why learn:

These are the two most common cases of systems without an API: a spreadsheet calendar and an ERP that only exports data.

Key concepts:

agenda.csv, erp-vendas.csv, read-only (N4).

What it is:

Run server.mjs with --selftest and see tools: 2, free time slots on 06/10, and TOTAL: R$ 856.00.

Why learn:

Test the bridge without any agent and without using up your quota.

Key concepts:

Self-test, proof, result checked by hand.

What it is:

The root .mcp.json already registers the bridge, and .claude/settings.json already allows it; claude mcp list confirms this.

Why learn:

Knowing where the connection is registered lets you replace it later with your own system.

Key concepts:

.mcp.json, enabledMcpjsonServers, Pending approval.

What it is:

Ask Claude for available times on 2026-10-07 and get 08:00 (Dr. Ana) and 16:00 (Dr. Bruno).

Why learn:

That’s Clara checking the calendar without opening the spreadsheet, and the answer matches the available rows in the CSV.

Key concepts:

claude -p, tool call, proof from the source.

What it is:

One command registers the ponte-modelo bridge in Codex, with the full path to server.mjs.

Why learn:

One bridge, two agents: you write the tool once and use it in both.

Key concepts:

codex mcp add, absolute path, $PWD.

View Full
2.3~35 min

🏗️ Your system’s bridge

Step 4 of R3: point the ponte-modelo bridge to your system’s export, change the columns, and keep everything read-only.

0 of 60%
What it is:

Find the file it exports in the system menu, with a header and in a fixed folder.

Why learn:

Without an API, the export is the bridge's raw material; its format determines how much adjustment will be needed.

Key concepts:

Export, header, delimiter, fixed folder.

What it is:

The PONTE_DADOS variable in the env field of .mcp.json, which makes the bridge read your folder instead of the examples.

Why learn:

Change the data source without touching the bridge code.

Key concepts:

Environment variable, .mcp.json, env field.

What it is:

A prompt that tells the agent to change only the column names used in run(), showing the before and after.

Why learn:

You adapt the bridge without coding, and the account rule stays the same.

Key concepts:

run(), column name, limit stated in the request.

What it is:

The R3 rule: a tool that reads is N4; a tool that writes counts as "modify" in POLITICA.md and requires approval first.

Why learn:

A read error gives you the wrong answer; a write error corrupts data that other people use.

Key concepts:

N4, N2, readFileSync, separate tool.

What it is:

Recalculate with a calculator the total the bridge calculates, line by line and by client.

Why learn:

A wrong column doesn’t cause an error: it gives you the wrong number that looks right.

Key concepts:

A verification account: proof, command → expected output.

What it is:

One line in the map with the path, level 6, the tool, the read policy (N4), and the test date.

Why learn:

A system without an entry isn’t used by the agent; the dated entry is what enables its use.

Key concepts:

CAPACIDADES.md, tested in, pending line.

View Full
2.4~35 min

🌐 Browser with policy

Recipe R5: agent-browser for systems that exist only as websites, with a written rule describing what the agent reads, fills in, and never does.

0 of 60%
What it is:

Computer use is step 5 on the ladder, the only one with low stability: the site changes and the automation gets lost.

Why learn:

If an API, MCP, CLI, or export is available, it takes precedence over the browser.

Key concepts:

Computer use, stability, selector.

What it is:

Two commands: install agent-browser with npm and download the Chromium it uses.

Why learn:

A separate browser without your logins is the safest way to get started.

Key concepts:

npm, Chromium, Claude in Chrome.

What it is:

Open example.com, read the title, and close it; the proof is the output Example Domain.

Why learn:

You verify the browser without clicking anything or sending anything.

Key concepts:

open, get title, close, R5 proof.

What it is:

The R5 request: read a website’s price table and return it as CSV, without clicking Submit or Purchase.

Why learn:

Reading is N4, filling in or sending is N2, and paying is N1; the request already says where to stop.

Key concepts:

Limit in the request, N4, N2, N1.

What it is:

The "Browser:" block from R5 pasted into AGENTS.md, which Codex reads and CLAUDE.md points to.

Why learn:

The rule applies to every request, even one you forgot to limit.

Key concepts:

AGENTS.md, @AGENTS.md, permanent rule.

What it is:

You log in; the agent doesn't ask for or store your password, and credentials don't pass from one tool to another.

Why learn:

In a logged-in browser, the agent can access everything you can.

Key concepts:

Credential, logged-in browser, POLITICA.md.

View Full
← Previous track: Discover Next learning path: Route and execute →