The whole picture.
And the follow-through.
Work coordinated. Results independently checked. Only the consequential calls come back to you.
A steering partner for your AI coding sessions
For the relentlessly ambitious.
Run more AI coding sessions without becoming their dispatcher.
Connect the Claude Code and Codex sessions you already run, across your accounts and machines. 2mw2lt steers them as one undertaking: it challenges the approach, has finished work reviewed by another vendor’s model, and carries each decision into the next brief. Only the calls that are yours come back to you.
See the desk at workStay in the work.Hold the standard.Keep the thread.
More work in motion. Less on your mind.
Agents multiply what you can do. 2mw2lt keeps it from multiplying what you have to carry.
- Where did we leave it?
- Is “done” really done?
- Which session owns this?
You.Still the connection between everything.
The whole picture.
You.Deep in the work. Not buried in it.See the difference
Stay absorbed. Not on call.
Connect your existing agent sessions across tools, accounts and machines. Your steering partner coordinates the work between them and brings you the trade-offs worth your attention.
Retry handling
Codex / Laptop
Changing the API client.Retry handling
Claude / Workstation
Changing the same client.Test coverage
Grok / Work account
Regression cases are ready.One builds. One challenges.
Two sessions. One implementation.
Keep regression tests moving.
Why this recommendation?
The reasoning, not just the answer
- The situation
- Both agents are changing retry handling in the same client. Separate activity reports look productive; together, they reveal duplicate work.
- The advice
- Keep implementation with Codex. Give Claude the independent review, while regression tests continue.
- A second opinion
- “Keep both streams of thinking. Give each a distinct job.”
The steering layer
Every lesson changes the next move.
2mw2lt connects what happened with what happens next. Independent judgment becomes a clearer brief, a better plan and work that moves within your mandate.
Design for solo users.
Independent critique caught two conflicting audiences. The decision now travels with the next brief: design for the person working alone.
Design for solo users. Independent critique caught two conflicting audiences. The decision now travels with the next brief: design for the person working alone.
Choose a thread. Trace what changed.You keep authority. The lesson travels.
A second mind. A higher standard.
Independent critique before committing effort. Independent review before accepting the result. A managed process that follows the work through, not a checklist for you to chase.
Find the question worth answering.
- The starting point
- “We need to tell our story.”
- The deeper question
- What will make someone recognise their own struggle?
- A direction to explore
- Show a scattered day becoming a clear next move.
Inspect the handoff
The standard travels with the work.
The brief, acceptance criteria and unresolved questions stay attached when the person or agent changes.
“Done” comes with something to inspect.
The independent review, checks and delivery outcome are part of the record, not another conversation to chase.
The next session
starts further ahead.
New session. Different machine. Still your train of thought. The intent, decisions and next step are there when you return.
“Make the first day
feel simple.”
The goal was confidence, not a completed checklist.
Start with a guided setup.
Guide the first steps. Save progress along the way.
Original decision. The rough thought stays attached.
Not just saved. Put to work. Decisions, runbooks, unfinished ideas and paths you ruled out. Curated against what changed, then brought into the next brief.
Follow the thinking
The intent
Help someone reach their first useful moment without getting lost.
The alternative
A compulsory checklist made setup complete, but delayed the reason they came.
What carries forward
Let exploration lead. Keep guidance close, preserve progress, and check the brief against the new flow.
Your reach should grow.
Not your coordination burden.
The horizon: your sessions, external machine swarms and trusted specialists, working from one shared intent. More capability without making you the dispatcher.
Make the first day feel simple.
Confidence, not a completed checklist.
One brief. Shared standards. Reviewed outcomes.- Explore
- Challenge
- Explore
- Reconcile
- Review
- Bring the craft
- Review
Different tools. One undertaking.
Research informs the flow. A separate session challenges it. The decision follows the work across accounts and machines.
What comes back becomes working knowledge for the next move.
Start with one repository.Keep the sessions you run.
2mw2lt is a plugin for Claude Code and Codex, and a desk at console.2mw2lt.com. You need macOS, uv and a repository on GitHub.
-
Add the plugin
In your terminal.
Claude Codeclaude plugin marketplace add endario/2mw2lt && claude plugin install 2mw2lt@2mw2lt --scope userCodexcodex plugin marketplace add endario/2mw2lt --ref main && codex plugin add 2mw2lt@2mw2lt -
Connect the repository
Open your coding tool in the repository and run this in its conversation. It signs you in, creates the workspace and starts this machine’s agent.
/2mw2lt:install -
Open your desk
Your sessions, their work and the calls that need you, in one place.
console.2mw2lt.com
Source-available on GitHub. Free for noncommercial use; commercial use requires a license.
A bigger idea.
Not a bigger burden.
What would you take on if keeping it all together stopped being your second job?
Pick the tension you know too well. Play with a different way through.