dotagent:port-fish-agent

To migrate a Fish-based agent to dotagent, you generate an agent.toml from the existing meta.json and integrate it with the current heartbeat and scheduling. This preserves the original agent behavior and enables seamless dotagent deployment without rewriting the core agent.fish.

Porting an agent.fish workflow to an agent.toml configuration involves mapping fields from the existing meta.json to the dotagent.toml format. This replaces direct Fish orchestration with dotagent scheduling for the agent lifecycle while preserving heartbeat semantics.

Yes, you can use dotagent scheduling to manage your existing Fish dotfiles agent. The migration enforces mapping from meta.json fields to dotagent.toml and preserves the original heartbeat semantics, ensuring consistent scheduling and notifications.

The best way to convert a dotfiles-based agent into a dotagent-managed agent is by generating an agent.toml from the meta.json file. This approach replaces direct Fish orchestration with dotagent scheduling while maintaining the original agent behavior.

Yes, you need to provide the meta.json file to port an agent.fish to dotagent. The migration workflow requires the meta.json to enforce the correct mapping of fields to the dotagent.toml configuration.