Skip to main content

Prerequisites and Required Tools

User module development for iAP is carried out using a set of tools centered on Visual Studio Code (hereafter VSCode) and Accel CLI, prepared on your local PC. This page organizes the tools required for the development environment and their roles, along with preparing the agents you will use.

Prerequisite knowledge such as CLI and terminal operations and where iAP fits in is summarized in Prerequisites. For term definitions, refer to the Glossary.

What You Can Do with This Guide​

By working through this guide, you will be able to accomplish one or both of the following:

  1. Set up a development environment using VSCode
    • Install the required tools in your development environment, launch VSCode, and create and build a new project for user module development.
  2. Migrate an existing project (created with e Builder) to a VSCode development environment
    • Add VSCode configuration and the assets required for AI-native development to an existing user module project, enabling editing and building in VSCode.

Target Audience​

This guide is intended for the following developers:

  • Developers who want to set up an AI-native user module development environment using VSCode
  • Developers who want to migrate an existing project created with e Builder to an AI-native development environment using VSCode
About "Supplementary notes that can be skipped"

This guide contains supplementary blocks with background knowledge and detailed term explanations that can be skipped. Reading all blocks including the supplementary ones on your first pass will help you understand the big picture. Once setup is complete and you need to reconfigure tools, you can skip these supplementary blocks and just follow the commands to work through the steps quickly.

Required Tools​

This chapter organizes the tools required for setup and their roles. It covers the required tools and their roles, as well as how the tools relate to one another.

Tool Roles and Relationships​

The development environment is built from a combination of tools. Here is an overview of what each tool does.

RoleToolDescription
Editor (IDE)Visual Studio CodeWhere you write code
Runtime / Package managementBun (v1.3.14 or later) / Node.js (v24 or later)JavaScript execution / dependency management
Build foundationJava (JDK)The foundation for compiling user modules
Build toolMavenUser module build / packaging management
Version controlGitManaging change history
Project initializationAccel CLICreating project templates / migrating existing projects
AgentGitHub Copilot / Claude Code / OpenAI CodexAI to support development

The role each tool plays is as follows:

  • Visual Studio Code: An integrated development environment for editing code. Development in collaboration with agents (vibe coding) is also done here.
  • Bun: A JavaScript runtime and package manager. Used to run Accel CLI (bunx) and to install dependencies and build (bun install / bun run build).
  • Java (JDK): The foundation for compiling user modules.
  • Apache Maven: A build tool that builds and packages user modules. It is invoked internally from bun run build.
  • Git: A version control tool for managing change history. Optional if you do not use version control.
Using Node.js

Accel CLI can also be used in a Node.js + npm environment. If you are using Node.js, substitute the following throughout this guide:

  • bunx @intra-mart/accel ... -> npx @intra-mart/accel ...
  • bun run build -> npm run build

The following diagrams show how the tools relate to each other.

Figure 1: Project Template Generation Phase​

These are the tools that run when creating a new project or migrating an existing one.

When the developer runs bunx @intra-mart/accel ... from the terminal, Bun fetches and executes Accel CLI, which generates the project template. Git version history is also initialized at this point.

Figure 2: Project Development and Build Phase​

These are the tools that run day-to-day after the project is created. The diagram separates the "development" and "build" phases.

The developer edits code in VSCode and develops while interacting with the agent. To build, run bun run build in the terminal (e.g., VSCode's integrated terminal). This invokes Bun → Maven → JDK in sequence, ultimately generating the user module (artifact).

Required Tools List​

CategoryToolMinimum versionVerification commandOfficial site
RuntimeBun1.3.14 or laterbun --versionhttps://bun.com/
RuntimeJava (JDK)8 or 11java -version· Oracle JDK: https://www.oracle.com/java/
· Amazon Corretto: https://aws.amazon.com/corretto/
· Red Hat OpenJDK: https://developers.redhat.com/products/openjdk
BuildMaven3.9.14 or latermvn --versionhttps://maven.apache.org/index.html
Version controlGit2.53.0 or latergit --versionhttps://git-scm.com/
IDEVisual Studio Code1.127.0 or latercode --versionhttps://code.visualstudio.com/
Available JDK versions

The available JDK versions differ depending on your target iAP version. Check the release notes for your target iAP version (intra-mart Accel Series document archive).

Required vs. Optional​

  • Git: Required if you use version control. If managing remotely on GitHub or similar, you will also need an account for the corresponding service.

Supported Agents​

This guide supports the following agents. If you develop using an agent (vibe coding), you can use any one of the following. Please have an account and subscription ready in advance before use.

AgentWhat you need to prepare in advance
GitHub CopilotA GitHub account with Copilot available (subscription/contract)
Claude CodeAn Anthropic account (a Claude subscription)
OpenAI CodexAn OpenAI (ChatGPT) account with Codex available (an OpenAI subscription)

You select the agent to use when creating the project. Depending on your selection, skill sets and other assets are placed in the .claude / .github / .codex directories.

When using GitHub Copilot CLI

GitHub Copilot CLI 1.0.61 or later is required. In versions 1.0.60 and earlier, the location from which the MCP configuration file is read is different, so it does not work correctly (the current GitHub Copilot CLI reads .github/mcp.json).

Account creation and subscription

For service subscription and account creation procedures, refer to the official information for each service.

Setup Flow​

Depending on your situation, there are two routes. Check which applies to you before proceeding.

If a problem occurs during the process

If you encounter a problem during any chapter, refer to Troubleshooting. It lists common symptoms, causes, and solutions.