Skip to main content
Sticky

Tailor IFS Cloud from the Inside, Faster with AI: Try Our New Preview and Share Your Feedback

  • Nov 2, 2026 1:21 PM UTC
  • 3 replies
  • 106 views

alhase
Sidekick (Employee)
Forum|alt.badge.img+5

AI coding assistants are already powerful partners for developers. With the right knowledge, they can help you tailor IFS Cloud from the inside, like an experienced IFS developer would.

An IFS Cloud Agentic Engineering Plugin is available as an early preview. It gives your AI assistant deep knowledge of IFS Cloud: our coding standards, how business objects are designed, and what your own development database contains. The result is tailoring that's right on the first attempt, with ideas turned into working customizations faster.

  • Bring your own AI: works with Cursor, Codex, VS Code, Claude Code and others, including autonomous agents running in a terminal.
  • Your data stays with you: runs on your own machine, reads the database read-only, and sends nothing to the outside world.
  • Better together with the IFS Cloud Development Kit: the plugin helps AI write the code, and the Development Kit adds IFS Cloud language support and code generation in VS Code. Use them together or on their own, alongside the tools you already know.

👉 Learn more and get started on the IFS Developer Portal.

As an early preview, stay vigilant of what your AI assistant produces, and keep human review checks in place.

 

Help us shape what comes next

This new capability is part of the journey of exploring new ways of tailoring IFS Cloud, and we'd like to build it with you. A few lines is plenty.

  1. Your experience: Tell us about a task you tried with the plugin. What did your AI assistant get right, and where did you still have to step in?
  2. Your reality: Walk us through your last IFS Cloud customization, from request to go-live. Where did the time and effort really go?
  3. Your ambition: If tailoring IFS Cloud took a fraction of today's effort, what would that unlock for your business or your customers?

You can follow where we're heading on the Interactive Roadmap (AI Code Editor for IFS Cloud Application Development). Your input is key to where this may, or may not, go next.

3 replies

dsj
Ultimate Hero (Partner)
Forum|alt.badge.img+22
  • Ultimate Hero (Partner)
  • Nov 4, 2026 11:05 AM UTC

​@alhase 

 

I tried the plugin with Codex with vscode. It connected to our build place environment database without trouble, and it handled simple code adjustments and code reviews well, with useful suggestions. Still haven’t used in a full scale development. But the tool is already proven to be good :)

 

I have few feedback points.

1. An AGENTS.md template for developers
The plugin has a lot of skills, and without knowing which skill is meant for which purpose, it’s hard for an outside developer to start using the tool out of the box in it’s full capalility. It would help if IFS provided an AGENTS.md template with the key instructions: when to use which skill, the standard workflows, and the rules to follow. Developers could then adapt it to their own needs.

2. One plugin for any coding agent
The plugin is currently packaged separately for VS Code, Claude Code and Cursor.

  • Do the skills differ between those packages, or is only the packaging different?
  • What’s the reasoning behind separate packages?
  • Would it be possible to offer a single plugin that works with any coding agent? (I had to switch to vs code due to no codex  plugin is available and hope the similar requirement would come from other agentic tool fans)

3. Bundle the code generation inside the plugin

Code generation currently depends on the VS Code extension. It would help if code generation were included in the plugin itself.

 

Cheers!

Damith


alhase
Sidekick (Employee)
Forum|alt.badge.img+5
  • Author
  • Sidekick (Employee)
  • Nov 16, 2026 8:50 AM UTC

Hi Damith,

Thanks for trying the plugin and for the clear feedback. Great to hear it worked well inside VS Code.

1. AGENTS.md template. Have you tried asking your assistant “get started with ifs-cloud”? It should give an overview and suggest workflow, and then each skill’s SKILL.md explains how it applies? Does that close part of the gap? What would a template most need to cover? If helpful, perhaps you could ask your AI agent to create a first revision of an AGENTS.md, test it yourself, and share here for feedback from a wider audience?

2. One plugin for any agent. The skills are the same in every package. Only the packaging differs, because each tool reads plugin files its own way. The wish for Codex packaging noted.

3. Code generation in the plugin. Today the plugin helps the AI write better IFS Cloud code, and the Development Kit is then envisioned to turn it into a verified, deployable result. The bundled code generation has been noted as future improvement opportunity.

When you try it on a full-scale development, a few lines on these topics would be helpful:

  1. How did the total effort compare with doing development with the plugin, vs without, and where did you still have to step in?
  2. When a customization gets done faster, who notices first: your team, through freed-up capacity, or your customer, through a lower cost or an earlier go-live?
  3. How is your team set up with AI assistants today: each developer’s own choice, or a shared setup for the team? And roughly how many developers work on IFS Cloud, and specifically how often on tailoring on the inside through customizations, relative to other types of tailoring?

Thanks again. This kind of feedback shapes the tools.

Best regards,
Alexander

 


dsj
Ultimate Hero (Partner)
Forum|alt.badge.img+22
  • Ultimate Hero (Partner)
  • Nov 17, 2026 2:14 PM UTC

Hi ​@alhase

Thanks for the detailed reply. We haven’t run it on a full-scale development yet, so I can’t give a fair comparison yet, but we’ll share one when we have.

We already have our own BMAD-style workflows and code generation and review skills that we have used for some time. We are now adopting the agentic plugin alongside them, so our use will be selective: we pick its skills where they fit rather than running everything through it.

That is why I asked for an AGENTS.md template. It would let us adapt it to our needs and state which skill is used in which workflow, instead of leaving the agent to choose. For example, some skills currently describe themselves as mandatory for every conversation or any creative work, which competes with our own workflows. A template showing how to set that precedence would help.

Hope you get what I’m trying to achive :)

 

Best regards,
Damith