Wire JEBAT into the editor the same way you operate the site.

A direct IDE integration guide for operators and developers wiring JEBAT context into their daily development tools.

Primary Editors

Integration Mode

Prompt + Rules

Outcome

Repo-Aware Coding

Rollout Guide

Adoption Checklist

guided

Setup

Gateway and IDE

Commands

CLI handoff

Models

Local posture

Operators

Team onboarding

Runtime Telemetry

Synchronized

Setup coverage90%

IDE integration84%

Command readiness86%

Guide focus

The editor should inherit the same operating posture as the browser layer.

JEBAT works best when IDE context, route architecture, and operator expectations are aligned. This page establishes that connection.

Install JEBAT prompts, rules, and operator context into the editor surface so coding sessions stay aligned with the workspace.

Keep CLI and browser entry points consistent so operators can move between chat, setup, and local execution without losing the thread.

Preserve coding rules, design constraints, and AGENTS guidance across VS Code, Zed, Cursor, and other supported tools.

Finish the setup with working commands and page-level validation so the environment is ready for actual implementation work.