What Agents Can Do

Ask in plain words. The agent opens with intellijsfcc_project_context, which picks the right chain of tools for the task, and follows it. Reads run at once. Anything that changes an instance starts as a plan the server checks before it runs, see Plans & Safety

Check for errors

"Check the sandbox for errors", "Fix the top production error"

1. intellijsfcc_project_context
2. intellijsfcc_issue_triage ranks the open issues by regressions, new ones, rises, count and severity, and resolves the top frames to files in your project
3. The agent edits the file, then intellijsfcc_change_verify checks it
4. After a deploy and a clean window of logs, intellijsfcc_logs_center_mark_fixed

The agent fixes one issue at a time, the most frequent first, and never marks one fixed before the fix is deployed and the logs stay clean

Which copy runs

"Which copy of Cart.js runs?", "Where does this template come from?"

intellijsfcc_file_overrides lists every copy of a path along the cartridge path, the one that runs first. intellijsfcc_path_resolve resolves */cartridge/... paths, templates and resource keys to the file the runtime loads, with the rule that decided

Templates, slots and content assets

"Where does product come from in this template?", "Which slot configurations use this slot?"

intellijsfcc_isml_variable_sources lists every isset of a variable. For one template it also shows what that template sees: its own variables, the templates that render it, the ones it renders and session variables. intellijsfcc_site_data_lookup follows a slot from its isslot tags to every slot configuration, with the template each one renders, and a content asset from its library to the code and slots that name it

The type of a value

"What type is basket here?", "Is this a dw.order.Basket?"

intellijsfcc_type_proof returns the type at a line and column, where it came from and each step that led there, such as a require or module.superModule

Change a route or override a model

"Add a check to Cart-AddProduct", "Override the product model in app_custom"

1. intellijsfcc_project_context
2. intellijsfcc_edit_prepare returns the effective file, where an override must go, the types in scope and the routes, templates and hooks around it
3. The agent edits or creates the override
4. intellijsfcc_change_verify checks the changed files: problems, unresolved requires and templates, and missing resource keys

The agent edits your override, never app_storefront_base, and keeps server.extend(module.superModule) in custom controllers

Ship and verify

"Upload the fix to the sandbox and check it"

1. intellijsfcc_remote_diff and intellijsfcc_change_verify, side by side
2. intellijsfcc_upload_plan or intellijsfcc_deploy_plan, then intellijsfcc_mutation_execute, which runs it at once
3. intellijsfcc_logs_center_watch_poll starts watching the logs
4. intellijsfcc_route_invoke requests the page
5. intellijsfcc_logs_center_watch_poll reports new errors, then stops

A new code version adds intellijsfcc_code_version_activate_plan before the page is requested. To move code from one instance to the next, the agent deploys to the lower environment first, see Several instances in one task

Logs

An agent keeps at most 3 log watches per project, and a watch stops after 30 minutes without a poll. Reports land in .intellij-sfcc/logs-streaming/reports/ in the project. See Fix with an AI agent

Files on the instance

"List the files in Impex/src", "Copy these images to the sandbox"

intellijsfcc_webdav_roots, intellijsfcc_webdav_list, then intellijsfcc_webdav_read_text or intellijsfcc_webdav_download. Writes go through intellijsfcc_webdav_mutate_plan, then intellijsfcc_mutation_execute, see Files & Deploys

Jobs, site archives and the page cache

"Run the catalog import job", "Export RefArch as a site archive", "Clear the page cache"

Every plan runs with intellijsfcc_mutation_execute. Running a job, an import and clearing the cache are Live change. An export is Instance write

B2C Commerce has no call that clears the page cache on its own, so the agent runs your cache job. When the project has no such job, the agent gets the Business Manager steps to clear it by hand

Jobs need OCAPI set up for the connection, see OCAPI & Jobs. intellijsfcc_ocapi_settings_preview writes the Data or Shop API settings with only the resources the plugin uses, for you to paste in Business Manager. It reads no credential. When a job or an activation is refused with 403, the answer names the missing resource and points to this preview

Sandboxes

"Start my sandbox", "Add 8 hours to zzrx-001", "Create a sandbox for this branch"

1. intellijsfcc_ods_list and intellijsfcc_ods_details
2. intellijsfcc_ods_action_plan to start, stop, restart or reset, or intellijsfcc_ods_update_plan to add hours, change the schedule or tags, or resize
3. intellijsfcc_mutation_execute runs the plan
4. intellijsfcc_ods_status until the sandbox is ready

To create one, the agent checks the realm with intellijsfcc_ods_realm_status, then plans with intellijsfcc_ods_create_plan. A new sandbox always has a time to live, never 0, and narrow API access. The preview shows what it costs and what data a reset or delete loses, with a warning when the sandbox is active, being debugged or watched

The agent prefers stopping to deleting. After a reset, the Log Center's stored logs of that sandbox are stale. See On-Demand Sandboxes

Live debugging

"Why is shippingCost empty at line 42?", "Debug Cart-Show on the sandbox"

• A one-shot capture: intellijsfcc_debug_capture_invoke stops at the line once, reads the variables and resumes
• A debug session: intellijsfcc_debug_status, intellijsfcc_debug_session to start, intellijsfcc_debug_breakpoint_edit, intellijsfcc_route_invoke in the background, intellijsfcc_debug_wait_for_stop, intellijsfcc_debug_inspect, intellijsfcc_debug_execution to step, then the agent removes its breakpoints

The debugger works on the active connection, see Debugging with Agents

Related