GitHub is bringing remote control to Copilot CLI, letting developers run and manage coding sessions beyond the local terminal. The move mirrors what Anthropic already introduced with Claude Code, as both push toward agents that can run and be steered from just about anywhere. 🔗 Read the full story here: https://lnkd.in/gfP2iQQ7
AI Native Dev’s Post
More Relevant Posts
-
GitHub Copilot is a pair programmer that suggests code snippets and full functions in real time inside your editor. It reads the surrounding code and comments to autocomplete patterns, draft unit tests, scaffold endpoints, and handle repetitive glue work. Best for developers who want to move faster and cut boilerplate without breaking flow. Use it to spike features, explore unfamiliar APIs, and standardize routine code. Guide it with clear function names and comments, review suggestions like any pull request, and keep security checks in place for critical paths. #GitHubCopilot #PairProgramming #DevTools
To view or add a comment, sign in
-
-
GitHub Copilot CLI Now Generally Available for Developers 📌 GitHub Copilot CLI is now generally available, bringing AI-powered code assistance directly to your terminal-no IDE needed. Devs can run complex tasks, explore codebases, and automate workflows with just a few commands. Say goodbye to context-switching and hello to smarter, faster shell operations. 🔗 Read more: https://lnkd.in/dr4rTZQ7 #Githubcopilotcli #Terminalai #Devopstools #Generativeai
To view or add a comment, sign in
-
Get GitHub Copilot directly in your terminal. It takes just seconds to get Copilot CLI running on your machine: 📦 Install via npm, Homebrew, or WinGet 🔐 Authenticate your GitHub account 🚀 Start coding No IDE required. No plugins. Just your terminal and Copilot — ready to code, debug, and explore your codebase from the command line. Credit: @GitHub #GitHub #Copilot #CopilotCLI #AI #DeveloperTools #Terminal #Productivity
To view or add a comment, sign in
-
I had some time on a flight back to Amsterdam, so I challenged myself to see how quickly I could vibe-code a solution to a small problem I kept running into. I work with coding agents a lot these days, and with CLI tools it can be hard to keep track of all sessions across a project. Introducing: Coding Agent Hub It is a lightweight Electron app that surfaces your coding sessions from Claude Code CLI and GitHub Copilot (with support for more agents coming). You can: - browse full session history - inspect token usage - open the related project in VS Code - resume a session directly in terminal It was built fast, so it is still a bit rough around the edges, but it is already useful (to me). If this sounds helpful, try it out: https://lnkd.in/eY8T_K9M #buildinpublic #electronjs #aiagents #githubcopilot #claude #developertools #vibecoding
To view or add a comment, sign in
-
𝗨𝘀𝗶𝗻𝗴 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗔𝗜 𝗺𝗼𝗱𝗲𝗹 𝗳𝗲𝗹𝘁 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲𝗹𝘆 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝗱𝗲𝗽𝗲𝗻𝗱𝗶𝗻𝗴 𝗼𝗻 𝘄𝗵𝗲𝗿𝗲 𝗜 𝘂𝘀𝗲𝗱 𝗶𝘁. I tried Opus 4.6 through GitHub Copilot (including plan mode), and also directly through Claude in the terminal. On paper, both should feel similar. In reality, they didn’t. Inside Github Copilot, even in plan mode, it still felt like an assistant. Helpful, responsive, and good at guiding the next step — but mostly reacting to what I asked. Using Opus directly in the Claude terminal felt different. It didn’t just respond. It started behaving more like a developer: • Breaking problems into smaller tasks • Deciding what to do next • Iterating on its own reasoning • Driving the flow instead of waiting for prompts That difference was subtle, but important. It wasn’t about capability. It was about how much initiative the system could take. Github Copilot felt like working with a smart assistant. Claude felt closer to working with a junior developer who can move things forward. Once you explain clearly to Claude what you want, then seems like developer beast mode kicks in. For simple tasks, both are great. But for more complex workflows, shift in behavior changes how you approach the problem entirely. Curious if others have noticed this — same model, different environment, very different working style. #AIEngineering #Claude #GitHubCopilot #LLM #SoftwareArchitecture
To view or add a comment, sign in
-
Codex vs GitHub Copilot: it is not really about which one is “better.” Both are strong. Copilot feels great for staying in flow inside the IDE, while Codex is better when you want to delegate bigger coding tasks, reviews, or repo-level work. The best choice depends on how you code.
To view or add a comment, sign in
-
Built a quick CI/CD cheatsheet while working through Github Actions on a personal project. 15 minutes to shift from "familiar with" to "can reason about". It's the kind of gap-filling that compounds when you're building full-stack applications.
To view or add a comment, sign in
-
Free-tier users really get no love 😅 Just ran a Plan + Start implement (4/5), and hit the limit right at the final validation step. With Agentic coding, a lot of the real learning honestly comes from paid usage. Without spending a bit, it’s hard to figure out the best way to actually use these tools. So far, GitHub Copilot still feels like the best option. But it really depends on your development workflow — you need to break down tasks well, plan things out, and feed enough context in one go to get good results.
To view or add a comment, sign in
-
-
GitHub Copilot upping its debugging game on the web is fantastic news for developers! Finding and fixing those pesky bugs just got a lot more streamlined, directly in the browser. Definitely makes the dev process smoother. Less head-scratching, more coding! 💻 #GitHubCopilot #WebDev
To view or add a comment, sign in
-
So, did GitHub just inject an ad in 1.5M pull requests? https://lnkd.in/dpQ2PNYu No, not according to their director of DevRel: "a third-party link was mistakenly displayed in a way that could be interpreted as a promotion." https://lnkd.in/dMgtauAv
Hey folks, had some conversations about this today so thought it would be helpful to be clear. GitHub does not and does not plan to include advertisements on the platform. We recently identified a programming logic issue in the GitHub Copilot coding agent that caused a 'product tip', including a third-party suggestion, to appear incorrectly in a pull request comment. This issue was introduced on March 24 during a rollout that expanded Copilot’s ability to contribute to any pull request when requested to by a developer. As a result, a third-party link was mistakenly displayed in a way that could be interpreted as a promotion. Our goal was to share novel ways to use Copilot coding agent, and in this case, we highlighted our integration with Raycast as part of a broader set of product tips, but this was surfaced more frequently than intended alongside other feature suggestions. We have removed Copilot agent tips from all pull requests moving forward. We appreciate the community flagging this and apologize for the error.
To view or add a comment, sign in
More from this author
Explore related topics
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development