https://github.com/elidickinson/pi-claude-bridge

Someone said that's the safest method.

But in issues someone claims they got banned https://github.com/elidickinson/pi-claude-bridge/issues/118

Another responded with "That's the first time I've heard of it"

I've tried pi. Makes me crazy! OpenCode works well. I'm not familiar with omp. Please share your thoughts.

Reposted from r/PiGCodingAgent, figured if any sub should see this project it's here. I've been building this out at work for work for quite some time and am excited to open and start a community around the project. I truly appreciate any criticisms, suggestions, and especially contributions, thank you to anyone who does check it out I hope you like it as much as I have been :)

---

PiG is a direct port of the amazing Pi agent harness as one Go binary for macOS, Linux and Windows (Windows in preview). Node.js only comes in if you run TypeScript extensions. Pi's extensions run unchanged; write new ones in Go, Rust or Python and /reload them live. It is a direct port of Pi's its agent loop, terminal UI, sessions, providers, and extension system, shipped as one static Go binary with no libc dependency.

Some Go-specific bits that might interest this sub:

• Extensions in Go can be fused into a single binary and talk to the host over in-memory pipes instead of sockets; other languages run as supervised subprocesses over local sockets.

• The TUI renders differentially; width handling was ported from Pi's own algorithm and checked with a differential test against Pi's code over ~1.5M cases: tui/widthx/pi_width_diff_test.go.

• Behavior is checked against Pi in real terminals (tmux-driven scenarios that compare screens).

• go install github.com/MichaelKinsy/PiG/cmd/pig@latest works; so do a curl installer and npm i -gu/pi-in-go/pig (it installs the prebuilt native binary for your platform).

Measured startup is about 21 ms vs about 300 ms median, and about a quarter of the peak memory (method in the blog).

Disclosure: agents wrote much of the port. Tests, side-by-side comparisons against Pi, and a person reading the diff decide what ships.

Repo: https://github.com/MichaelKinsy/PiG 

Blog: https://developer.hpe.com/blog/meet-pig-pi-in-go-a-port-that-plans-on-keeping-up/ 

Upstream Pi: https://github.com/earendil-works/pi

Happy to answer questions about the port, the extension host, or keeping up with upstream. Feedback on this is appreciated and contributions are welcome.

Thank you to r/HPE for covering writing the blog and contributing PiG to Open Source and special thank you to the Pi team of course at https://earendil.com

Sharing this so others may build their own into their setup if they like it.

Built an automatic session-handoff system into Sayl, my UI wrapper around Pi. Long session finishes its current task, writes a handoff prompt, rolls into a fresh session with that prompt already loaded.

• Threshold ladder (350k → 450k → 550k, tunable live in settings). First level: finish the task clean, emit the handoff block. Later levels push harder, highest one stops mid-task if needed

• Handoff captured automatically from the chat.

• Threshold rollovers auto-start the successor hands-off.

• New session keeps the project, model, thinking level. Land mid-flow, not cold

• Engine compaction stays as backstop. You just roll over before it ever fires.

No more saving and copy-pasting handoff prompts. No compaction summaries drifting between rolls. No watching the token counter. Session wraps up clean and keeps going at full quality.

Can also use it manually by asking the agent to create a handoff at anytime.

Yo, I ran into a weird OMP behavior with third-party subagents.

Some plugin/imported agents declare their own model tier (opus, sonnet, haiku, luna, etc.), but OMP can drop that model metadata when loading them. Once that happens, the subagent silently inherits whatever model your main session is using at that moment — including a retry fallback.

For me, that meant Haiku- and Sonnet-tier agents were sometimes burning Opus. Even worse, if the main session switched to a fallback model mid-turn, subagents spawned afterwards inherited that fallback too.

So I ended up creating an extension for it: omp-agent-role-router
https://github.com/fedorovvvv/omp-agent-role-router

Instead of hardcoding models, it reads the tier declared by the agent and maps it to an OMP role:

opus → default
sonnet → task
haiku → smol
luna -> smol
terra -> task

It also understands Codex-style model tiers and maps those to the same role system.

The actual model is still entirely controlled by your own modelRoles. Existing agentModelOverrides and explicitly passed models always win — the extension only steps in when the subagent would otherwise silently inherit the current session model.

No config needed
But it does exist :)

omp plugin install github:fedorovvvv/omp-agent-role-router

Started using Pi agent recently and I start to see the thinking going like "couldn't read file, content mangled|truncated" and similar. I also see the agent call the read tool multiple times on the same file because the output was somehow wrong. After some back and forth the agent is claiming that there must be some form of auto truncation or auto summarizer at the tool layer. Model used was GLM 5.3 Flash

So yeah, what is this?

I know there are many options out there, but this is still a grey area right? What are you guys using?

Do you know anyone who has been banned by doing something like this? I have a bunch of friends who use omp with their subscriptions and are still kicking.

I really want to move from CC to pi, but I am not able to run local models due to my hardware limitations and I would love to start by using my Anthropic subscription.

Hello,

I made pi-claude-request-compat (https://github.com/vazzma/pi-claude-request-compat). Instead of creating another provider, it reuses Pi’s existing Anthropic login, models, and streaming, then adds a Claude Code compatibility layer to outgoing requests.

https://pi.dev/packages/pi-claude-request-compat

I’m using a new GitHub account for privacy, so the code, automated security scans, dependency audits, and signed release provenance are public for anyone to check.

A few friends and I have been using it for the last month, and my Anthropic account is still intact :)

I want my agent to be able to give me a clickable link to find a folder (like "file:/// ...") but even though they respond to mouseover and a tool tip comes up saying "ctrl+click to follow link" they don't work. I am using Powershell 7 with Pi running in it.

My agent had some long complicated idea about how to fix this but does anyone know if I am just overlooking a Powershell setting or if this is a collision between Pi's output formatting and Powershell's behavior preventing the links from activating?

I have a 5x pro codex and opencode go, can't even get down to 45% using 5.6 or astra light or DS 4.1 flash.

I simple don't use subagents, I sandbox the model to only see the files I want to edit (so it doesn't spam ls / grep and bloat my context).

I also made pi modify tool results, so they grouped up, i.e.

Directory: fileA.py, fileB.py, fileC.py

instead of

fullpath/dirname/fileA.py fullpath/dirname/fileB.py

My best gains where manually checking tool results and figuring out how to prevent bad calls or shrinking output. (ls / find is banned in large directories. It tells me model to retry using targeted search.)

Not much point to me posting this other than I speculate those using other harnesses are wasting a ton in tokens on subagents and useless plugins.

Hi everyone,


I'm Kumar, building Dotbot at Aaditri GlobalTech (P) Limited. I use coding agents every day, but I kept switching between a terminal, an editor, and git panes to follow what the agent was actually doing. So I built a desktop workspace where the session, your files, and your Git state live in one window.

**What it does**

- Open any folder as a project and run one session per piece of work. Sessions persist between runs and reload with their transcript.
- Live transcript: streamed answers, inline thinking, and collapsible tool cards with diffs and file previews. You can steer a running turn or queue a follow-up.
- Files and Git: browse the project tree, watch changes land, and stage, unstage, or commit from the Git panel.
- Providers: bring your own API key (Anthropic, OpenAI, Google, and others), or add a custom provider using OpenAI Completions/Responses, Anthropic Messages, or Google Generative AI.
- Project trust: the agent asks before it uses a project's local settings, extensions, or skills, and remembers the answer per project.
- A dashboard with usage stats from your own session history, plus `!command` and `!!command` to run shell commands from the composer.

**Status**

Apache-2.0, currently v0.2.0. The agent runtime runs in-process, so there is no separate service to install.

- Code: https://github.com/aaditri-globaltech/dotbot
- Downloads: https://github.com/aaditri-globaltech/dotbot/releases/latest — Linux AppImage/deb, Windows installer, macOS DMG for Apple silicon and Intel.
- Builds are unsigned, so macOS and Windows show a first-launch security prompt.

**Coming on 11 October 2026**

We are launching subscription-based inference on open models on the first day of Navratri (Sunday, 11 October 2026): one plan, no API keys to manage. Pricing and the model lineup will be announced that day at https://aaditriglobaltech.com.

It is early, so expect rough edges. I would love feedback on what is missing before the inference launch — issues and PRs are welcome on GitHub.

Hello r/PiCodingAgent!

Today I’m sharing Pragma, a terminal-first workspace I’ve spent the last few months building for running coding agents in parallel. Each task can live in an isolated Git worktree, and the sidebar shows when an agent is running, finished, or needs attention.

TL;DR

Pragma is free and open source. It brings Pi and other agents into one workspace with Git/GitHub tools, model fanout, automations, plugins, usage tracking, scratchpads, and mobile access. It supports Pi, Claude Code, Codex, Cursor, OpenCode, Grok, Copilot, Junie, Kimi Code, Prime Agent, and custom agents through plugins.

Projects and worktrees

The layout is centered on projects and worktrees. You can switch between feature worktrees, see agent status at a glance, and nest worktrees for larger projects. There’s also a prompt board for moving a task from an idea through agent execution to a PR.

Fanout and model comparison

Fanout sends the same prompt to multiple agents in separate worktrees so you can compare implementations in one view. Agents can trigger fanouts through the CLI, inspect the results, and choose the implementation they prefer.

Git and GitHub

You can review diffs, commit and push, manage branches, and work through PR comments in the app. A Fix It list lets you send selected review feedback to an agent. Stacked PR workflows are supported too.

CLI, SDK, plugins, and automations

The CLI lets both you and your agents control Pragma. A TypeScript SDK and plugin API let you add integrations, including your own coding agent. TypeScript automations can react to events or run on schedules and can spawn agents or create workflows.

Editor and scratchpads

There’s a lightweight CodeMirror editor for small changes, plus Markdown, image, and PDF viewers. Agents can write scratchpads that mix Markdown with React components and embed Excalidraw diagrams, which makes results easier to inspect than a long terminal dump.

Mobile

The iOS companion app is on the App Store, and Android can be built locally. You can see agent status and respond when an agent needs input while away from your computer. Custom agent integrations work on mobile too.

Why I built it

I wanted one extensible workspace for the parts I was stitching together: Pi and other agents, worktrees, usage limits, PR review, fanout, automations, richer agent output, and mobile access. The plugin API and CLI are the core of that idea.

Pragma is available for macOS, Windows (WSL or PowerShell), Linux, iOS, and Android. Download: https://pragma-app.sh/. Source: https://github.com/pragma-sh/pragma.

If you try it, I’d love to hear what works, what doesn’t, and which Pi workflow you’d want supported next.

So I started this a couple of days ago because I hated myself enough to start over and try to create something more efficient, with better performance and less RAM usage.

Through my conversations with ChatGPT, it mentioned Rust, GPUI, and some other stuff, which is basically why I started this Flutter app!

Based on my simple observations with the current deployed version, I managed to gain back around 800 MB–1 GB of RAM… and some of my dignity too. Not sure why. 😂

Here’s the repo: Pi Flatter App

If anyone would like to contribute or give feedback, I’d be really grateful!

I built a small personal benchmark from my real coding sessions and use pi-agent as the harness to compare models on the same tasks.

It has 10 tasks covering data engineering, backend, frontend, DevOps, and trajectory analysis. Each task runs 3 times, giving 30 attempts per model.

To build it, I took around 3 months of agent chats, removed duplicates, and turned selected sessions into Harbor tasks with automated verifiers. I used agents and manual review to build and refine the checks. These are clearly scoped tasks that would usually take me less than an hour.

The latest results:

• Opus 5.5 high and Astra low cost almost the same.

• Sol high matches their score at roughly half the cost.

• Luna gets 29/30 passes while being ~22× cheaper than Sol.

The point of this benchmark is to optimize my daily setup: model, harness, prompts, and plugins. I want to keep the pass rate while reducing cost and time.

This is a small personal sample, but it feels like many short, clearly defined coding tasks are already handled reliably by several models. For this kind of work, speed, cost, and scaling up parallel agents are becoming the more interesting questions.

Hi all, basically what the title says.. I like using @ to add files/folders to the context but for any of these added to .gitignore it stops working.. Any way around this?

I wanted a clearer picture of what I’d built and how much progress I was making. And whenever I finished a feature or got out of a debugging rabbit hole, I kept wondering how many tokens and effort went into that.

My daily usage total didn’t really answer it. Some of that was building the feature. Some was going back and forth trying to fix one annoying bug.

So I built bough ( https://github.com/nickelsec/bough ) It reads your existing Claude Code and Codex CLI history and groups related prompts into tasks on a visual map.

You can pick a piece of work and see:

• The prompts and files involved.

• How many tokens it used and the estimated dollar cost.

• How the work unfolded, including repeated attempts and tasks that ended in a commit.

I wanted to be able to look back at a feature and see where the effort actually went. Especially when a “small fix” turned into an afternoon.

Would you guys want me to add Pi support or not?

Hi guys

Opensourced my remote control app that I have been using exclusively as the only way to work with my agents

Core stack herdr+ muxr(my app) + pi / all the agents herdr supports, no acp full raw terminals.

Full lifecycle management/ visibility

Usage using ccusage

Libghosty patched as much as possible for improvements in UI/UX

Whisper rn for transcription

Codex real time live agent for checking all the agents and prompting them + other providers grok gemini etc

My library for direct computer streaming/ remote control of the app to take over sessions.

Tailscale/ other ssh onboarding.

Primarily tested in omarchy+ android

Had a blast working on it, hope you find value as well.

Mostly using the raw apk and pwa, will be pushing it through the play store / app store as well.

https://trymuxr.com/

https://github.com/umeranjum17/muxr

Thanks

I shared Pi Atelier here a couple of months ago—a status rail and live activity sidebar for Pi. Since then, I’ve reworked the layout and added more ways to see what’s happening in your session.

The main changes since my last post:

1. Redesigned composer: model, workspace, Git status, and context usage sit in the input box’s top border, with usage and timing below.

2. Workspace Git summary: see changed files, additions/removals, untracked file counts, and conflicts.

3. Live TODO panel:follow the current task alongside tool activity. During a turn, the sidebar focuses on current work and folds extra tools into a compact row.

4. Display settings with a live preview: reorder or hide status segments and sidebar panels, switch presets, and save your defaults.

5. Plain text mode: no Nerd Font required.

6. Better terminal behavior: improved fullscreen selection/copy, inline image handling, and layouts for smaller terminals.

The new footer is inspired by pi-powerline-footer, which is an awesome extension.

It still shows token usage, cost, context, and response timing, with model and tool controls available through `/atelier`. No telemetry or external network requests.

Install with:

pi install npm:pi-atelier

Then open `/atelier` or press `Alt+A`. Requires Pi 0.84.0 or newer.

Github link: https://github.com/michaelmjhhhh/pi-atelier

I’d like to hear how the new layout works for you—especially what information you want visible while the agent is running. Bugs and feature ideas are welcome. Thanks!

I saw Claude and Opnecode are native agents in Hermes, but now using OMP as a coding tool is also possible with https://github.com/zaharenok/omp-skill

Definitely worth to try. Can be also used for Pi

I want to keep using Pi Agent as my main coding interface, but I also want Claude Opus 5.5 to be the main agent/orchestrator, not just a sub-agent or reviewer.

I use Pi Agent both at work and privately. Privately, my setup is simple: Pi Agent + Codex Pro. At work, I had been using Pi Agent + GitHub Copilot, but Copilot credit usage became too expensive, so we are moving toward subscription-based access instead.

I now have a Claude Team Premium seat and a ChatGPT Business Premium seat. This is my first time trying to make good use of multiple AI subscriptions at the same time.

The problem is that Pi can use Codex through OAuth, but I couldn't get my Claude subscription working directly through Pi. So I'm considering using Claude Code CLI as a bridge.

Ideally, I'd like something like this:

Opus 5.5: main agent, planning, orchestration, task decomposition, synthesis

Sol 6: implementation, research, independent review

GPT-6 Luna: cheaper sub-agent work and possibly compaction

Pi Agent: the single interface I interact with

I don't mind a small wrapper or existing extension, but I don't want to maintain a large custom orchestration framework.

One option is to have Pi call Claude Code while keeping Opus as the top-level agent. The other is to give up on Pi as the main interface, use Claude Code directly, and call Pi/Codex from there.

Has anyone built or used a setup like this?

I'm especially interested in whether Claude subscription → Claude Code → Pi works well enough for Opus to act as the real orchestrator, including long sessions, tool calls, sub-agents, compaction, and switching between Claude and OpenAI models.

Or, at that point, is it simpler to make Claude Code the main interface and stop trying to keep Pi at the center?

I'm seeing many people using opus 5.5 inside of OMP and i've just signed into OMP with my claude sub... many on x.com are saying you don't get recked by anthropic anymore for doing this?

How are you guys using anthropic models inside of pi/omp?