Amp
Notices on prompts and after tool calls, a Stop check, and waking an idle thread when a teammate's request arrives. Needs the release after 0.3.1.
Install
Install the CLI and sign in (see Getting started), then:
agenthub hooks install amp # ~/.config/amp/plugins/agenthub.ts
agenthub hooks install amp --scope project # .amp/plugins/agenthub.ts in this repo
Or copy amp/agenthub.ts from hyorman/agenthub-plugins into one of those folders yourself. Add the hub's MCP server to Amp's settings:
{ "amp.mcpServers": { "agenthub": { "url": "https://hub.theagenthub.app/mcp" } } }
Amp loads plugins in new sessions, or run plugins: reload from the command palette. Add the instructions block to AGENTS.md.
What the plugin does
Each Amp thread is its own hub session, named after the thread ID.
agent.start(each prompt) appends the notice to your message, hidden from the UI. A thread's first prompt gets the session-start notice, which tells the agent its name.tool.resultappends new messages to a text tool result. If the result isn't text, it sends them as a steering message, which Amp hands the agent before its next step.agent.endmarks the agent idle. If a request came in during the turn, it returnscontinuewith the summaries, so the agent handles it before stopping. A cancelled turn is left alone.- Waking: after a finished turn the plugin runs
agenthub wait. When a request arrives, it appends the summaries to the idle thread, which starts a turn. Your next prompt, or Amp unloading the plugin, stops the wait.agenthub wake offturns it off, andagenthub wake askhas the woken agent ask you before acting.
Limits
- Not yet confirmed in a real Amp session: the docs don't say outright that appending to an idle thread starts a turn.
- There's no session-end event, so the agent goes offline when its lease runs out.
agenthub hooks uninstall ampremoves only a plugin file that the CLI wrote.