PTENES
TRACK 2 · TIER B + A

⚡ Real Productivity

Genuinely useful (Tier B) and nearly at the top (Tier A): parallel workflows, isolation, cloud review — and the honorable mentions that almost made the Top 12.

Orchestrator launches N agents agent agent agent agent agent … Result in parallel
2
Modules
12
Topics
~1h30
Duration
Interm.
Level

Trail map

Detailed content

2.1~45 min

⚙️ Workflows, isolation, and review (Tier B)

The genuinely useful features: dynamic workflows with hundreds of agents, isolated worktrees, cloud review, deep research, the browser, and the B ecosystem.

What it is:

Claude writes a script that spins up to 1,000 agents for massive jobs, processing them very effectively in parallel.

Why learn:

When a task is huge and divisible, parallelizing cuts the total time. It’s the foundation for several features listed above.

Key concepts:

Uses a lot of tokens; it’s new and still finding its place in everyday use.

What it is:

Runs agents in ISOLATED copies of the repository so they never collide, then merges everything at the end.

Why learn:

Important when working on a team or on several features at once, so one agent doesn’t step on another’s work.

Key concepts:

Isolation up front, merge at the end—safe parallelism.

What it is:

Slash command that spins up a FLEET of agents in the CLOUD (like code review) to check every bug before reporting.

Why learn:

Fewer false positives: each finding is checked before it reaches you.

Key concepts:

Runs in parallel in the cloud — it doesn’t block your terminal.

What it is:

You ask for research and it automatically invokes a dynamic workflow, spreads searches across the web (and your apps), and returns ONE cited report.

Why learn:

Deep research without opening 30 tabs; sources are included.

Key concepts:

Advanced Research on the same parallelism engine.

What it is:

A sidebar that clicks, fills out forms, and acts across tabs; and Computer Use (point and click) to use any app when there’s no connector.

Why learn:

Extends Claude’s reach to everything in your browser or on your screen.

Key concepts:

A connector when available; point and click as a universal fallback.

What it is:

Projects (workspaces with chats, files, and instructions together), Memory (pulls in context from old chats), and /recap (shows what the session was doing when you come back).

Why learn:

It’s the everyday glue: reusable context and frictionless pickup, great when you have lots of tabs open.

Key concepts:

More: Artifacts & Interactive Charts, Browser Recording, Claude for M365, Mobile Push, Cross-Device Convo and Connectors Directory.

View Full
2.2~45 min

🥈 Almost at the top (Tier A)

The honorable mentions that almost made the Top 12: Workspace from the terminal, dispatch and channels, desktop app and design, plan/auto mode, hooks and effort, and the visibility layer.

What it is:

Runs Gmail, Drive, Docs, Sheets, and Calendar through the TERMINAL; you can build skills around it.

Why learn:

Proves Claude can drive any CLI—your office workflow becomes automation.

Key concepts:

Technically, it’s not an official Claude “feature,” but it’s so useful that it earns honorable mention #1.

What it is:

Dispatch: start a task on your phone, and Claude runs it on your desktop and sends you the result. Channels: connect Telegram, Discord, or iMessage to a live session.

Why learn:

Good for continuing the conversation from your phone and talking to the session from wherever you are.

Key concepts:

Channels works both ways: you send and receive.

What it is:

Desktop App: a Mac/Windows home for chat, Cowork, connectors, and managing local and cloud routines in one place. Claude Design: describe what you want, and it creates polished designs/slides/one-pagers.

Why learn:

The desktop app is also better for copying and pasting text without the terminal's weird wrapping; Design is great for teams.

Key concepts:

Design: comment, view design systems, and generate PPTs quickly.

What it is:

Plan Mode: researches and proposes a plan before touching anything. Auto Mode: approves safe actions and blocks risky ones without constantly asking.

Why learn:

Planning ahead prevents rework; Auto Mode removes the friction of approving everything all the time.

Key concepts:

Auto Mode is, in practice, a permission level.

What it is:

Hooks: automatically run your own commands on session events. Effort Levels: adjust reasoning depth from low to maximum (/effort).

Why learn:

Automate the surrounding workflow and calibrate how much brainpower the task deserves.

Key concepts:

Ultracode: the maximum-effort tier — reasoning at full throttle + automatic multi-agent workflows.

What it is:

Agent View (dashboard of all terminals/agents running in the background and their status), /btw (a parallel question without interrupting the task) and /context (what's filling up the window).

Why learn:

You can see what’s running and how much it costs, and control it.

Key concepts:

More: /usage, Prompt Caching (reuses repeated context and saves tokens), and /background.

View Full
← Track 1 · The Foundation Track 3 · The Top 12 →