Customer Success Engineer

JetBrains Air brings multi-agent control to JetBrains IDEs. JetBrains just announced JetBrains Air, a product system designed to run and manage AI coding agents across individual developers, teams, and entire engineering organizations. Get Free Daily Insights to Stay Ahead in Your Entrepreneurial Journey. Table of Contents Three products, one system. Air ships as three distinct layers: * Air in JetBrains IDEs: a free plugin, now in public preview, that runs Claude Agent, Codex, Junie, Copilot, and OpenCode inside PhpStorm and other JetBrains IDEs. You can run multiple agent sessions at once, review diffs with the IDE's native tooling, and connect via your own API keys, existing subscriptions, or JetBrains AI credits. * Air Teams: shared cloud environments where developers and agents work together on tasks, with automations for code review and release notes. Currently in early access. * Air Governance: model and agent permissions, spending limits, and usage analytics for org-level control. Previously called JetBrains Central. Vendor-Agnostic by design. Air works with third-party agents out of the box. Agents that support the Agent Client Protocol (ACP) connect directly to the IDE without extra configuration. JetBrains CEO Kirill Skrygan was direct about the strategy: BizStack build its own agent, and BizStack intend to make it excellent. But JetBrains Air does not require customers to use ours, and its strategy does not depend on which model provider leads the rankings this quarter. The free IDE plugin is available now at the JetBrains Air website, where you can also sign up for Air Teams early access. Cagri Sarigoz ( Founder) I'm founder of BizStack at Cagri Sarigoz LLC and a passionate advocate for entrepreneurs. With over 14 years in tech, marketing, and AI, including my role as Head of SEO at CitizenShipper and co-founder of TaleBot at Intale AI, I'm dedicated to sharing genuine, useful product insights and tips. At BizStack, I aim to cut through the digital noise to provide clear, actionable advice. And more than all else, I'm a father to a (always) little girl and a husband. Contact me at [email protected] for assistance.

JetBrains joins Python Asia Organization as a Gold Sponsor. Python Asia is welcoming JetBrains as a Gold Sponsor of Python Asia Organization (PAO). JetBrains builds professional tools for developers and teams around the world. In the Python community, many people know the company through PyCharm, its professional Python IDE for web development, data, machine learning, and other Python workflows. That gives JetBrains a clear connection to the ecosystem PAO works in. But the reason this sponsorship matters to Python Asia goes beyond developer tools. It helps support the people and communities doing the work between conferences: organizing meetups, sharing lessons, introducing communities to one another, and finding better ways to collaborate across borders. JetBrains, PyCharm, and the Python Community. PyCharm has been part of the Python developer landscape for years. Developers use it across web development, data, machine learning, and day-to-day Python work. It brings coding, debugging, testing, project navigation, and other development tools into one environment, whether someone is working on a small project or maintaining something much larger. JetBrains' connection to Python also extends beyond the product itself. The company has supported developer and open-source communities, including organizations within the Python ecosystem. That matters to PAO because regional community building depends on the same kind of long-term thinking. Events are important. So is everything that happens before and after them. Connecting Python communities Across Asia. Python Asia Organization works to bring Python communities across East and Southeast Asia closer together. Those communities do not all operate under the same conditions. Some have established conferences, strong volunteer networks, and long-standing sponsor relationships. Others are smaller, newer, or working with fewer resources. Organizers face different challenges depending on where they are, but many of the problems are familiar: finding speakers, keeping volunteers engaged, funding events, sharing knowledge, and reaching beyond their local networks. There is a lot communities can learn from one another. PAO tries to make those exchanges easier. That might mean bringing organizers into the same conversation, sharing an opportunity across countries, helping one community learn from another, or creating programs where people can hear directly from the teams doing the work. Sometimes it becomes a formal collaboration. Sometimes it is simply an introduction that would not have happened otherwise. Both matter. The work that happens between conferences. Conferences are often the most visible part of a Python community. People travel. Talks happen. Organizers finally meet people they may have known online for years. A few days can create conversations and relationships that would have taken months to form remotely. Then everyone goes home. The work does not stop. Someone starts preparing the next meetup. Another organizer is looking for a speaker. A community is trying to improve its sponsorship process. Someone else is working out how to make an event more accessible, recruit more volunteers, or avoid a mistake another group has already learned from. This is where regional relationships become useful. An idea tested in one country can save another community weeks of work. An introduction can turn into a speaker exchange, a partnership, or a future event. A conversation that starts casually can become something much bigger later. A large part of PAO's work happens in these smaller moments. Python Across Asia gives communities a place to talk about what they are building, what they have learned, and the people behind the work. The PythonAsia conference creates a different kind of opportunity: a shared regional gathering where those relationships can happen face to face. They are different programs, but they come from the same idea. Communities are stronger when they do not have to work in isolation. Why this sponsorship matters. A useful sponsorship should do more than put a company logo on a website. For PAO, sponsorship gives Python Asia more room to keep doing the work that is harder to see from the outside: connecting organizers, running regional programs, maintaining partnerships, sharing opportunities, and helping communities reach beyond their usual circles. The results are not always easy to measure in a single number. Sometimes two organizers meet and decide to work together. Sometimes a community finds a speaker through another country's network. Sometimes someone discovers a conference outside their own region, attends it, volunteers, speaks, or brings an idea home. None of those things looks especially dramatic on its own. But repeated often enough, they change how communities relate to one another. That is how separate local groups begin to feel like part of something regional. What JetBrains' Gold Sponsorship supports. PAO is still building. There are more communities Python Asia want to reach, more organizers Python Asia want to connect, and more opportunities to create for people working across the region. JetBrains' Gold Sponsorship helps give Python Asia the capacity to keep that work moving through PAO's programs, events, partnerships, and community initiatives. For Python Asia, the goal is not simply to run more activities. It is to make regional collaboration easier to access and easier to sustain. Python Asia want organizers to know who they can turn to outside their own country. Python Asia want communities to be able to share what they have learned instead of solving the same problems from scratch. And Python Asia want more people to discover the work happening across Python communities in Asia. That takes time. It also takes partners willing to support the work behind the scenes. Python Asia is glad to welcome JetBrains as part of it. Support Python communities Across Asia. Organizations interested in supporting PAO can learn more about sponsorship and how that support helps create more opportunities for Python communities across East and Southeast Asia.

Huntress targets agentic cybersecurity as revenues rise. JetBrains launches local command-line proxy to help control AI spend. 21st September 2026 With more AI in integrated development environments (IDEs) and developer tools than ever, vendor JetBrains is thinking up ways to tackle rising AI costs. Via the JetBrains blog, Viktor Kiselev and Mikhail Filippov said that, rather than limiting tool choices to shrink management overhead, JetBrains developed a local command-line proxy, JetBrains Central CLI. It routes requests from CLI coding agents. As a result, developers can run terminal agents easily, using their preferred model. And there's "virtually no administrative friction and no more waiting weeks for approvals", Kiselev and Filippov said. Therefore, managers can create and view reports in a central console. That includes current, historical and forecast AI consumption and costs for departments and shows AI costs and use by developer, agent and IDE. In addition, all the data can be aggregated with other AI expenses, using an analytics API. And you can set specific kinds of AI limits across every agent, IDE, developer, team or group, they said. Kiselev and Filippov admitted their AI development expenses were 10 times higher as of August. And that all happened in the previous six months. "When the costs started rising, we realised that we didn't know how to control them systematically," they said. Control AI costs, retain choice. The blind spot was partly because JetBrains developers also use non-JetBrains AI tools. And they choose the tools they want to use themselves, so they can select the best for each task. Most of them use between three and five AI tools in a given month, Kiselev and Filippov wrote. "They're using its IDEs as much as ever. They've added more command-line interface (CLI) agents, agentic development environments, for running several AI agents in parallel, and IDE-integrated AI tools. "Governing developers' AI usage shouldn't mean cramping their workflows," they said. JetBrains had already been collecting consumption statistics and other metrics from the server side. Then they processed them into separate, highly elastic storage. Also, they'd been applying AI credit budgets to their own tools, they said. Because more organisations were adopting generative AI, increasingly multiple models, AI costs had "skyrocketed", they said. In particular, Anthropic's release of Claude Opus 4.5 and 4.6 spiked token consumption, they said. "JetBrains developers began using these models in various places, like Claude Code CLI, the AI chat in JetBrains IDEs, and Junie. After that, usage started almost doubling every month," they said. "Soon enough, we hit 150 Claude Code seats and moved onto the Enterprise plan with rates based on API usage. That's when costs really took off." Third-party AI tools considered. JetBrains' previous management console hadn't covered third-party AI tools. Meanwhile the mix of tools kept changing, they said. As a result, JetBrains Central CLI was built, essentially after repurposing a personal debugging tool. "The CLI currently supports three of the most popular terminal agents. Four more are in internal beta," they noted. However, niche setups and personal AI subscriptions will remain out of scope. "As our goal is to cover the AI traffic running through the tools developers most rely on," they added. Security 9th September 2026