{{ message }}
Repository navigation
ABAP: Failed to create custom agent: java.lang.RuntimeException: Invalid workspace folder URI:semanticfs:/<project> #82
Description
Feedback source
None
GitHub Copilot plugin version
0.15
Eclipse IDE and version
Eclipse Platform 2025-09 with ABAP Development Tools
Platform
Microsoft Windows NT 10.0.22631.0 x64
Steps to reproduce
On the Custom Agents tab, click "Add...", enter a name, choose your ABAP project, and confirm.
Logs (optional)
No response
Expected behavior
New agent gets added to the list of agents and the Markdown editor opens.
Actual behavior
Error message:
Additional information
It works in non-ABAP projects.
Activity
jdneo commentedon Apr 28, 2026
related with #60
ethanyhou commentedon May 9, 2026
Hi Jascha Schröter (@MergingMonkey),
We've just released GitHub Copilot for eclipse 0.17.0 that contains several improvements for ABAP. Could you please try this version and check whether the issue is now resolved?
FrankBerwanger commentedon May 19, 2026
Hi I just checked it with version 0.17.0. The error still exists.
MergingMonkey commentedon May 19, 2026
Ethan Hou (@ethanyhou),
Thanks, but it says my company disabled the setting 🙁
Just to be sure: Which setting controls this, so I can check on the Copilot settings page?
bkrencker commentedon May 19, 2026
Hi, I am having the same issue when I try to add custom agents to the ABAP Development Tools in Eclipse Copilot.
Workstation: Windows Server 2022 21H2, x64 with Eclipse 2026-03 and Github Copilot 0.17.0.
I get the same error message with "invalid workspace folder URI".
In the log file there is following entry:
!ENTRY com.microsoft.copilot.eclipse 4 0 2026-05-19 10:43:11.387
!MESSAGE [Error] Failed to add mode
!STACK 0
java.util.concurrent.CompletionException: java.lang.RuntimeException: Invalid workspace folder URI: semanticfs:/ED6_100_1234_de
at java.base/java.util.concurrent.CompletableFuture.wrapInCompletionException(CompletableFuture.java:323)
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:359)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:364)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1791)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1781)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:511)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1450)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:2019)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:187)
Caused by: java.lang.RuntimeException: Invalid workspace folder URI: semanticfs:/ED2_010_8724_de
at com.microsoft.copilot.eclipse.core.chat.service.FileBasedCustomModeService.getAgentsDirectory(FileBasedCustomModeService.java:43)
at com.microsoft.copilot.eclipse.core.chat.service.FileBasedCustomModeService.lambda$2(FileBasedCustomModeService.java:116)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1789)
... 5 more
Caused by: java.nio.file.FileSystemNotFoundException: Provider "semanticfs" not installed
at java.base/java.nio.file.Path.of(Path.java:210)
at java.base/java.nio.file.Paths.get(Paths.java:95)
at com.microsoft.copilot.eclipse.core.chat.service.FileBasedCustomModeService.getAgentsDirectory(FileBasedCustomModeService.java:40)
... 7 more
ethanyhou commentedon May 20, 2026
Hi Jascha Schröter (@MergingMonkey),
This setting is setup by your enterprise admin. If you are the owner of your enterprise repository, you can refer to this doc to enable custom agent.
jdneo commentedon May 21, 2026
hi all,
Custom agents in abap project is not supported yet. We are still finding proper solution for that.
HuprichT commentedon Jul 13, 2026
Sheng Chen (@jdneo) Is there way to subscribe to this topic? Any kind of Feature Roadmap or something like that?
kecinzer commentedon Oct 15, 2026
+1
juangabrielsanchez-jti commentedon Oct 15, 2026
Hi all,
As a workaround, you can create a non-ABAP project, and create the custom agents there. They will then be available generally, even when working on other ABAP projects.
Best regards.