Skip to main content

Overview

AgentUse can execute agents directly from HTTPS URLs, enabling:
  • Shared agent libraries
  • Version-controlled agents
  • Community agent repositories
  • Dynamic agent loading
Remote agents must use HTTPS and have the .agentuse file extension for security.

Running Remote Agents

Basic Usage

With Arguments

Security

Remote agents run with the same permissions as local agents. Always review the agent content before execution. Only run agents from trusted sources!

Security Prompt

When running a remote agent, you’ll see a security prompt:
Options:
  • p or preview - Show the agent content before deciding
  • y or yes - Execute the agent immediately
  • N or no - Abort execution (default)

Performance

Remote agents are downloaded and executed directly without caching. Each run fetches the latest version from the URL, ensuring you always run the most up-to-date agent code.

Publishing Agents

GitHub Repository

  1. Create a repository for your agents:
  1. Access raw files:

GitHub Gist

  1. Create a Gist with your agent
  2. Get the raw URL
  3. Share the URL for others to use

Self-Hosted

Serve agents from your server:
For local development, AgentUse allows HTTPS URLs with localhost or 127.0.0.1 and will accept self-signed certificates for these addresses only.

Versioning

Using Git Tags

Version in URL

Advanced Usage

Dynamic Loading

Load agents based on conditions:

Agent Composition

Remote agents as sub-agents:

CI/CD Integration

For automation, you can use expect or other tools to handle the security prompt:

Best Practices

AgentUse enforces HTTPS URLs to prevent man-in-the-middle attacks. HTTP URLs will be rejected.
Remote agents must have the .agentuse file extension for security validation.
Use the preview option to review agent code before execution in untrusted environments.
Include version information in URLs or use Git tags for reproducible deployments.
Clearly document what MCP tools and environment variables your agent needs.

Example: Shared Team Agents

Repository Structure

Team Usage

Troubleshooting

  • AgentUse only accepts HTTPS URLs for security
  • Ensure your URL starts with https://
  • HTTP URLs will be rejected with an error
  • Remote agents must have the .agentuse file extension
  • Ensure your URL ends with .agentuse
  • Ensure you’re using the raw file URL, not the GitHub page URL
  • For GitHub: use https://raw.githubusercontent.com/...
  • Check if the repository is public
  • Verify the branch/tag name
  • Verify the URL is correct and accessible
  • Check if corporate proxy or firewall is interfering
  • Ensure the remote server has valid SSL certificates

Security Checklist

  • Only run agents from trusted sources
  • Use the preview option to review agent code before running
  • Ensure remote URLs use HTTPS and have .agentuse extension
  • Implement access controls on agent servers
  • Monitor agent execution logs
  • Rotate API keys regularly
  • Use environment-specific agents
  • Verify server SSL certificates are valid

Next Steps

Sub-Agents

Compose agents together

Examples

See remote agent examples