PyCharm for AI-assisted Django Workflows

Summary

According to the 2026 Django Developers Survey, ninety percent of respondents incorporate artificial intelligence into their weekly or daily workflows. While agents generate code rapidly, developers remain accountable for understanding, evaluating, and shipping changes within their applications. PyCharm addresses these demands by integrating support for external agents, local models via Ollama and LM Studio, and customizable agent skills across codebases. The IDE maintains version-specific framework assistance, including auto-completion for Django 6.0 template partials, alongside architectural inspection tools and visual diffs. Furthermore, developers can trace application components, inspect API endpoints, execute HTTP requests, and query database migrations directly through built-in tooling.

Context

The 2026 Django Developers Survey indicates that 90% of respondents use AI weekly or daily, yet developers remain accountable for reviewing and understanding agent-generated code across evolving framework versions.

Approach / What changed

PyCharm integrates multi-agent choices, local model connections via Ollama and LM Studio, reusable skill repositories, visual review tools, Local History, Django architecture visualizers, and database inspection tooling.

Takeaways

• PyCharm 2026.2 adds native skill support for Claude Agent and Codex, allowing developers to configure reusable instructions per project or globally.
• Local History operates independently of version control, enabling developers to restore code states from before an agent modified files without prior commits.
• PyCharm tracks framework updates directly, providing code completion for Django 6.0 template partial tags that may not exist in an agent's training data.

Related reading

• Dropbox · May 28, 2026

  Beyond code generation: rethinking engineering productivity in the age of AI agents

  Dropbox shares how widespread AI code generation shifts software development bottlenecks downstream into code review, CI infrastructure, and validation pipelines. To adapt, they built Nova, an internal coding agent platform that safely automates scoped tasks such as migrations and flaky test remediation. They also evolved their developer productivity framework to measure end-to-end customer impact and code quality rather than simple pull request throughput.

  Ilya Yakovlev,Andrew Cheung,Binoy Dash,Simran Jumani,Dmitriy Meyerzon,Mark Breitenbach,Ishan Mishra,Kazuaki Okumura

• Grab · Jun 22, 2026

  Scaling out Distroless adoption With AI

  Grab is transitioning its microservices to Distroless base images to eliminate unnecessary binaries and reduce vulnerability risks, but the migration risks runtime failures from missing shared objects and system utilities. To safely validate container execution in continuous integration without staging dependencies, the team relied on medium tests that run containerized services alongside internal dependencies managed by Testcontainers. Because hundreds of services lacked this test harness, Grab implemented an agentic workflow using Claude Code and Model Context Protocol integrations to inspect repositories, generate test boilerplate, and resolve configuration errors. Once test baselines are established, an automated patch-test-compare pipeline updates Dockerfiles, constructs multi-stage builds for necessary dynamic libraries, and creates draft merge requests for human approval.

  Jia Yee Chong

• Grab · May 15, 2026

  Scaling developer experience: How we improved Android Studio in a large monorepo

  Grab's passenger Android monorepo contains roughly 2,000 modules and 11 million lines of code, leading to IDE sync times exceeding 35 minutes on cold starts. While Bazel handles application builds, Android Studio relies on Gradle sync to construct its project model, requiring Gradle to evaluate every module during configuration. To solve this bottleneck, the team built a custom Focus plugin that restricts IDE syncing to target modules and their direct dependencies. The architecture reuses a static dependency graph generated during existing Gradle-to-Bazel migration tasks to eliminate the Gradle configuration phase during module selection. An IntelliJ extension and a Groovy method-shadowing technique in settings.gradle allow developers to configure focused modules directly through a graphical user interface.

  Rifqi Fahmi

• Jetbrains · Aug 24, 2026

  Junie Can Now Run Entirely on Your Mac – No Credits, No Cloud

  JetBrains has introduced Junie Local, a feature that runs the Junie coding agent entirely on local hardware without cloud dependencies, subscriptions, or credit meters. Users execute a single command inside Junie to download a 4-bit quantized Qwen3.6-27B model, requiring an Apple M5 Mac with 64 GB of RAM. The team prioritized prefill throughput over pure generation speed by utilizing 8-bit arithmetic instructions on the M5 Neural Accelerator, which increased prefill throughput by approximately 40%. Performance optimizations also include KV-cache reuse, speculative decoding to double generation speed, and disabling reasoning to preserve performance. In JetBrains' evaluations, the local configuration performed comparably to cloud-based Sonnet 4.5 on everyday tasks while ensuring source code, diffs, and prompts never leave the local environment.

  Dmitry Savelev