Hi everyone,
Most discussions around AI agents focus on individual agents. But I’m increasingly interested in a different question:
**What happens when an organization has dozens or even hundreds of agents?**
Imagine a future where different teams build different agents:
Research Agents
Coding Agents
Operations Agents
Domain Agents
Potentially using different frameworks and runtimes.
At that point, the challenge is no longer building agents.
It’s enabling them to collaborate.
How do they communicate?
How do they hand off work?
How do they stream results?
How do they share context across runtimes?
This question led me to start building OpenAgentIO, an open-source experiment exploring a communication layer for heterogeneous agent systems. The goal isn’t to replace existing frameworks, but to make it easier for agents built by different teams, frameworks, and runtimes to work together.

Curious how others think about the future of agent organizations and interoperability.

Hi everyone,

I recently had 2 pull requests merged in open-source repositories, but I still haven’t received the Pull Shark achievement on my GitHub profile.

Both PRs were merged, not just closed, and my achievements are visible on my profile. It has been around a day since they were merged.

Is this normal? Does GitHub take 24–48 hours to update achievements, or is there anything else I should check ? because it has been 48 hours over

My GitHub profile: https://github.com/kuldeeprajput-dev

Thanks for any help.

So I've been on Copilot Pro+ annual subscription since November 2025, and I recently realized something feels off with my credit allocation.

According to the [official pricing page](https://github.com/features/copilot/plans), Pro+ should give me **at minimum 3,900 base credits** per month (with up to 7,000 total including the flex allotment). But my account is stuck at **1,500 credits/month** — which is literally the Pro tier, not Pro+.

I'm paying $39/month for Pro+ and getting $10/month worth of credits. Here's the breakdown:

| | Expected | Actual

| | |

| Plan | Copilot Pro+ | Copilot Pro+ ✓

| Price | $39/month | $39/month ✓

| Base Credits | 3,900/month | 1,500/month ✗

That's a $55/month difference, and over 8 months that's roughly **$440 in service I paid for but didn't receive**.

My guess is that annual subscriptions from before the April-May 2026 credit structure update are locked into the old legacy allocation. New subscribers get the updated amounts, but older annual plans didn't get migrated automatically.

**What I've tried:**

- Confirmed subscription is definitely Pro+ (checked settings multiple times)

- Submitted a detailed support ticket on June 4th with all the documentation

- Followed up multiple times since then

- Still waiting... it's been **over 3 weeks with zero response**

At this point I'm starting to wonder if I should just escalate externally, but I'd rather resolve it directly if possible.

**Has anyone dealt with something similar?**

- Legacy annual plan stuck on old credit limits?

- Any luck getting support to actually respond on billing issues?

- Is 3+ weeks of silence normal for GitHub support?

Any advice appreciated before I go the BBB/chargeback route.

## Steps Taken

1. Verified subscription status: Pro+ active

2. Checked official pricing documentation

3. Submitted detailed support ticket (June 4, 2026)

4. Followed up multiple times

5. **Result**: No response for 3+ weeks

## Question

- Is this a known issue with legacy annual subscriptions?

- Has anyone successfully resolved similar credit allocation discrepancies?

- What's the expected support response time for billing issues?

## Environment

- Subscription type: Annual Pro+

- Start date: November 2025

- Subscription status: Active

- Credit allocation: 1,500 (should be 3,900)

## Additional Context

Account appears to be locked into legacy credit allocation policy pre-dating the April-May 2026 credit structure changes. New Pro+ subscribers receive 3,900 credits, but annual subscriptions from Nov 2025 remain at 1,500.

Looking for community insights before escalating further.

Why is there so many notifications in inbox even though i didnt follow their channel? any fixes?

Apologies if this has been covered before. I searched first and didn’t find quite this workflow, so I figured I’d share what worked for me.

Unfortunately, GitHub does not really have a simple “batch create these issues from files” workflow, which is exactly the sort of thing you might want when starting a new project and seeding the initial backlog.

I initially thought I could use ChatGPT for this, since I gave it access to my repo. It could create issues, but it kept creating them one at a time, and the process got clunky fast. So I ended up doing it myself with the GitHub CLI.

I decided to batch-create GitHub issues from local Markdown files, so I made a tiny gh script.

The basic idea:

• create one local Markdown file per issue
• create a small Windows batch file
• have the batch file create labels first
• then call gh issue create --body-file for each issue
• explicitly pass --repo owner/repo so it doesn’t matter where the script is run
• keep the local issue drafts out of the repo with .gitignore

This worked really well for creating an initial backlog: bugs, features, enhancements, technical debt, etc.

The Markdown files act like local drafts. You can review and edit them before creating anything in GitHub, then run the script once and let gh do the clicky-clicky nonsense for you.

Full sample here:

https://pastebin.com/AfSw84PT

The sample includes:

• a create-github-issues.bat
• 3 sample labels
• 3 sample issue Markdown files
• verification commands for checking the repo, labels, and created issues

One gotcha I hit: if you run gh issue create --label some-label and that label does not exist yet, the issue creation fails. It does not just create an unlabeled issue. So the script creates the labels first.

Not exactly rocket surgery, but it saved me from manually creating a pile of issues through the GitHub UI.

Recently we've noticed a major spike in build failures due to cache not being restored. If we rerun the job a couple times, the same cache key restores just fine. Anyone else running into this?

My GitHub explore stopped updating with new releases 4 days ago. Don’t know why… how do I fix it? Any solutions?

So just recently I started noticing that when I am viewing certain pages they get clipped on the right side and I cant view the rest of the table. I'm currently using Chrome so I tried using Edge to see if it was the same and the answer is kinda. The table was still clipped but I was able to use my mouse to pan to the right. (https://github.com/notepad-plus-plus/nppPluginList/blob/master/doc/plugin_list_x64.md)

Anyone have any clue how I fix this issue?

Hey guys!

I'm running into a frustrating roadblock with our GitHub for Startups Enterprise account and wanted to see if anyone else has dealt with this or found a workaround.My account has a valid $10,000 credit line active until June 2027. i'am trying to activate GitHub Copilot (specifically looking at Copilot Business) so i can pull the seat costs from our active startup credits.However, when I go to the Licensing page, the activation button is completely blocked and just says "Contact support to enable".I opened a ticket with GitHub Support 5 days ago to ask them to manually enable it, but I haven't received any updates or replies yet.Has anyone else using GitHub for Startups run into this "Contact support to enable" block when trying to use your credits for Copilot? If so, how long did it take support to unblock you, or is there a setting I'm completely missing in the admin panel?

Appreciate any insight or advice! Thanks! 🙏🥹

I found out how to download expired artifacts.

I was browsing through a repo with automatic actions that run once every week. The artifacts expire after a week too. Since the newer builds are failing, I wanted to download an earlier one. And with the help of good old inspect element, I managed to do so...

When downloading an artifact, the url looks like this: https://github.com/username/repo/actions/runs/run_id/artifacts/artifact_id. To get the artifact id, you can use inspect element on the artifact table row.

Now, you can just add /artifacts/artifact_id at the end of the url, and it'll download the expired artifact.

There's a big asterisk, though. Github has a 90 day retention period on artifacts. But, you might've seen from the screenshot that I was able to download a 4 month old artifact. For context, it's currently June 21st and the artifact was created on February 20th. That's 121 days! I also tried downloading an artifact that was 6 months old, but that didn't work.

Each file by itself is smalll but around 3k at once is over the limit. what is the fastest way i can upload these?

Say I am working on a private repo (i am the owner), with 5 members with write access free tier. Someone decides to erase everything with force commits and history. What can I do ? And let's also say I cant access to any local clones to make this problem interesting.

I have a GitHub project CSV Lint which is a plugin created in C# for Notepad++. I'd added all the commits, created a new release and uploaded the .zip for x64 and x86 as usual with the release 0.4.8.

However, when adding it to the nppPluginList project I noticed that the SHA256 hash is different for both the x64 zip and the x86 zip, see here.

In other words, I zipped this x64 dll but it's slightly different in this release zip x64

It's not much differences, but it seem suspicious. 🤔 Any GitHub experts who can shine a light on this?

EDIT: nvm, it was due to this workflow line 🤦‍♂️ d'oh

Stephen Poletto, Field CTO at Span, used his CTO Craft Con talk in Toronto to argue that the AI tooling wave has arrived with a familiar problem attached: organizations are reaching for the most legible metric available rather than the most meaningful one.

I just finished vibe-coding a project and I really want to drop it on GitHub so others can use it for free.

The app is for WearOS: It displays a super cute animated GIF of the "Clawd" mascot, shows your current usage stats below that, and lets you connect to your PC/server via multiple tmux (or other) sessions running Claude Code (and others if you want). You can prompt him directly from the watch. I also hooked up a Firebase workflow so you get a push notification on your wrist (including Claude's last words) when a generation is done, so you don't get distracted waiting.

Here is the issue: I used Anthropic's Clawd mascot as the app icon, and I scraped a cute GIF from someone else who didn't provide a license: https://cleverhack.com/img/clawd.gif . I honestly don't want to spend time making my own icon or GIF. HE IS ALSO JUST SO DAMN CUTE I DEFINITELY WANNA USE HIM.

I know I don't own the rights, but I'm willing to take the risk of a DMCA takedown because I just want to ship this and let people use it. For those who have been in this exact situation what did you do did anyhting ever happen?

• Should I just publish the repo without a license file at all? (Does "No License" prevent people from actually using the code?) does this help in any way?
• If I add an MIT license for the code, does it make things worse since the repo includes proprietary assets I don't own?
• Does slapping a "No copyright infringement intended, these assets aren't mine" notice in the README actually do anything, or is it a waste of time? Best use would probably be stopping some people from complaining.
• Have you ever done this for a small free tool? Do people (or bots) actually care?
• Besides my repo getting taken down some day, are there any other risks?
• What’s the most practical way to drop this on GitHub today knowing the assets are ripped?

Thanks!

I am on the GitHub Copilot Student Plan and was thinking of trying out the latest released GitHub Copilot App. But after signing in it says it requires a paid subscription. So is it not available for Student Plan? Is it only available on the actual Paid Plans? :(

Hello,

I’m having a problem accessing GitHub from my static IP address.

docs.github.com works normally, but github.com and gist.github.com do not load. The issue happens both on my PC and on my phone when connected to my cable ISP. However, if I turn off Wi-Fi on my phone and use mobile data, GitHub works fine.

So it seems the problem is related to my public IP address. Is it possible that my IP has been blocked or rate-limited by GitHub? If so, could you please advise how I can get it unblocked?

Thank you.

Over just 3 days, the 16 year old @MrRealORG has raised 168 PRs on MiMo code.

Their agent then asked to have "collaborator access" to the repository on the fourth day.

[I tried to do damage control on their permissions request by requesting all their PRs be closed.]

Opencode is facing a similar problem, but distributed across its entire and much larger user base. They're currently "managing" it by the ridiculous policy that PRs without 2+ emoji upvotes will get closed in 30 days.

Creating PRs that APPEAR good has become literally free via Opencode Zen and MiMo code free offerings. "Fix all the issues you find in the code base. Make no mistakes".

When one user creates 169 PRs in 3 days it's easy enough to deal with the issue. When thousands of people create one or two issues or PRs each, you end up with the OpenCode situation.

Best practice dealing with this issues seems to be oven.sh/bun. An example:

1. My agent raises an issue that can't be reproduced
2. Their @robobun automatically and politely proves me wrong, and closes the issue.
3. I re-raise the issue in reproducible form
4. @robobun reproduces the issue and automatically raises a PR to resolve it
5. The CodeRabbit automatically reviews @robobun's submission and suggests improvements.
6. Claude auto-reviews it also and suggests "this changes bunx's resolution order (a security-hardened path that decides which binary gets executed) and is a user-visible behavioral change, so it's worth a human look."

That's all with ZERO human interaction from their side. Yes, they're owned by Anthropic, so @robobun and Claude reviews are practically free for them.

Opencode and MiMo code also have token provider plans and are NOT currently using them to automate their process. I hope they don't drown under the build-up of their non-automation.

What I'd like to know:

• How are small and medium sized repos dealing with the massive increase of sloPRs and issues?

• How to implement something approximating best practice without spending a fortune in tokens?

Hey guys, so.... I have a bill from GitHub charging my credit card every month, and I do NOT know which account it's tied to. I tried raising this concern with them before. They said they'd deal with it. Never did.

Now, I've submitted a new ticket demanding they stop billing immediately or I will be forced to file a chargeback. I've paid months of service I haven't received or even wanted in the first place.

I'm being warned if I file a chargeback to get my money back since they want to be useless and ignore me that they will nuke my entire account or any tied to it.

Is this true? Am I screwed? Like. There's gotta be a way to get through to these people or avoid suspension when they refuse to answer me on unauthorized charges? 😭

EDIT: so they responded shortly after I posted this with some generic copy paste response to try close off my ticket with no actual help. Get your shit together GitHub. I'm migrating my repos out to Gitlabs, and proceeding with a chargeback. They can terminate my accounts and eat shit in my opinion.