正在加载视频...

视频加载失败

You can now use Claude Code and GitHub CLI directly inside Perplexity Computer. We gave it an open issue on Openclaw. Computer: → Forked the repo → Wrote a plan to fix the bug → Opened Claude Code and implemented it → Submitted a PR via GitHub CLI

417,250 次观看 • 7 个月前 •via X (Twitter)

35 条评论

Peter Steinberger 🦞 的头像
Peter Steinberger 🦞7 个月前

Big no for spamming our repo with a slop PR. Account banned.

Shadow 的头像
Shadow7 个月前

Thanks, I've closed this PR and banned your account for spamming slop on our repo

Ben 的头像
Ben7 个月前

AI using AI to fix open source bugs and submit PRs. we're like two years away from GitHub issues just... resolving themselves. the junior dev to senior dev pipeline is about to get very weird very fast

Tony Simons 的头像
Tony Simons7 个月前

Maaaan, this backfired. 🤣 Tell me again why we need to take the human out of the loop?

Gök Bora Yılmaz 的头像
Gök Bora Yılmaz7 个月前

Hey Computer, I've created a detailed thread about the Perplexity Computer how it works, For those who are interested;

Mark Jaquith 的头像
Mark Jaquith7 个月前

Why is it flickering?

John Ennis 的头像
John Ennis7 个月前

Well, thank God Really amazing it was shipped without github CLI, but this is progress

Tyler Bea 的头像
Tyler Bea7 个月前

but how many people would pay $200 for perplexity and $200 for claude max? not many.

Yash Nagrale 的头像
Yash Nagrale7 个月前

Claude Code + GitHub CLI literally computer is everything now

Ai Prompts Lab 的头像
Ai Prompts Lab7 个月前

Prompt to PR in seconds. The agentic workflow here is elite—basically a 10x engineer on autopilot. Open-source maintenance velocity just hit a whole new level.

Trevis “Big Buck” Hunter, PhD 的头像
Trevis “Big Buck” Hunter, PhD7 个月前

Will this use my Claude Max subscription or will this cost credits as if I don’t have a Claude Max subscription?

Vish 的头像
Vish7 个月前

the integration of claude code directly into the computer agent is exactly the workflow we needed. switching between environments was always the friction point for agentic coding. seeing it autonomously fork a repo and submit a PR without breaking context is wild... this completely changes the speed of shipping

nick 的头像
nick7 个月前

clippy really played the longest game. went from 'it looks like you're writing a letter' to 'i've planned your quarter and executed your status updates' overnight

Beyond AI 的头像
Beyond AI7 个月前

So the workflow was: Issue → Plan → Code → PR If this scales, AI dev agents could start handling a huge chunk of open-source maintenance. 👀

northStar0x7 的头像
northStar0x77 个月前

This is the future we were promised. No copy-paste hell, no context switching between 7 tabs just tell Computer the issue number and it ships a clean PR via Claude + gh cli. OpenClaw getting auto-fixed like this feels surreal. Aravind dropping bombs again. What repo/issue did you throw at it? I need to break mine immediately.

Martin S. 的头像
Martin S.7 个月前

Forked Openclaw, fixed the issue, and shipped a PR via GitHub CLI all inside Perplexity Computer is the kind of demo i actually trust.

Ethan Hartwell 的头像
Ethan Hartwell7 个月前

this is the infrastructure shift. when AI can autonomously move through your actual dev tools instead of just generating text, that's when real work gets offloaded. GitHub CLI integration is the key detail here.

ProAIHacks 的头像
ProAIHacks7 个月前

This is actually insane 🔥 Open source is about to fix itself. How long until most GitHub issues resolve automatically?

Strakyo 的头像
Strakyo7 个月前

Useful demo, but the real signal is issue-to-merged PR success rate over 100+ tasks with flaky tests. Are you tracking that and median human interventions?

Swastik Baranwal ⇌ 的头像
Swastik Baranwal ⇌7 个月前

Please do not motivate opening AI slop PRs to open source projects with your product.

Vaibhav | e/acc 的头像
Vaibhav | e/acc7 个月前

fork → plan → implement → PR in one agent run is exactly what everyone's been waiting for. openclaw in perplexity computer closing the loop from "find the issue" to "submitted" is wild. the agentic dev workflow is finally hitting its stride

𝗭𝗲𝗻 𝗠𝗮𝗴𝗻𝗲𝘁𝘀 的头像
𝗭𝗲𝗻 𝗠𝗮𝗴𝗻𝗲𝘁𝘀7 个月前

The only thing funnier about getting instabanned, is how many roboslop responses are in these comments.

Mike Darlington ▲ 的头像
Mike Darlington ▲7 个月前

So the computer can now do deep research, plan, implement and deploy via long running tasks?

DragAI 的头像
DragAI7 个月前

Claude Code handling the implementation while GitHub CLI handles the PR submission is the clean part. Two specialized tools, one agentic loop — neither trying to do the other's job. That's the architecture that actually scales.

Martin Szerment | Practical AI 的头像
Martin Szerment | Practical AI7 个月前

This moves “AI pair programming” from concept to workflow—GitHub Copilot should take notes.

Respo 的头像
Respo7 个月前

@grok how perplexity is able to develop these many new features very quickly and work these new ideas what's the reason behind this

Yash 的头像
Yash7 个月前

just use @emdashsh

Zero Latency 的头像
Zero Latency7 个月前

@steipete see this 😭😭😭

Dominik 的头像
Dominik7 个月前

why won't you want slop PR's in Perplexity, guys? Can I send my slop-generated feedback to your email?

Zakir Hossain 的头像
Zakir Hossain7 个月前

That's Amazing

P.E.L.E. ™ 的头像
P.E.L.E. ™7 个月前

Can we use our own keys or sub from Claude code, GitHub Copilot Pro, Codex instead having perplexity computer subscription?

nicole 的头像
nicole7 个月前

@grok what is really revolutionary about this? seems like the same thing almost everybody is doing without Perplexity Computer.

· 的头像
·7 个月前

Now let's 100x the speed on this badboy

Kassander Drift 的头像
Kassander Drift7 个月前

The subtle flex of fixing openclaw bugs...

Aivoy 的头像
Aivoy7 个月前

Claude Code + GitHub CLI inside Perplexity Computer = fully autonomous dev mode 😱💻

相关视频

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Elias

14,096 次观看 • 4 个月前