A ready environment for coding agents doing Power Platform and Dataverse work: the tools they need, kept current, and Claude Code and GitHub Copilot set up with the TALXIS/skills plugin. Wherever the agent runs, it gets the same tools.
Don't run coding agents directly on your own workstation. They run arbitrary commands. Give them a sandbox: About cloud and local sandboxes.
Codespaces or any devcontainer tool. Your .devcontainer/devcontainer.json needs only the image:
{ "name": "Power Platform", "image": "ghcr.io/talxis/tools-agentbox/image:latest" }Composing your own instead? Each tool is a Feature; add agentbox to keep
them current. On Windows, use Dev Containers: Clone Repository in Container Volume rather than
opening a Windows folder: Linux line endings and file modes, and much faster.
GitHub Copilot cloud agent. Add a step to your .github/workflows/copilot-setup-steps.yml:
- name: Set up AgentBox
run: curl -fsSL https://talxis.com/agentbox-setup | bashClaude Code cloud environment. In an org-shared cloud environment:
- Setup script:
curl -fsSL https://talxis.com/agentbox-setup | bash - Environment variable:
CLAUDE_CODE_PLUGIN_SEED_DIR=/usr/local/claude-plugin-seed - Network access: Custom, with the defaults, plus
cli.github.comandtalxis.com. With a stricter list, setup also needsghcr.io,pkg-containers.githubusercontent.com,api.nuget.org,registry.npmjs.org,packages.microsoft.com,releases.hashicorp.com, anddot.netwithbuilds.dotnet.microsoft.comwhen the machine lacks .NET 10. - The setup script fails when a tool didn't make it, so a broken environment shows in its log.
- Optional: to update the tools as sessions start, merge the hook in
session-start-hook.jsoninto managed settings.
Tools that follow their latest release update on every container start. Mid-session:
agentbox prerequisite updateThe agentbox CLI also checks a machine (prerequisite validate,
harness validate). The contract lists what stays stable. The tools are listed in
agentbox-features.json.