The assistant
Terminal agent detection
The assistant · 1 min read
If you start an AI tool in Agentfly's terminal, Agentfly notices and offers to share what it knows about the project with it.
When you would want it
So the assistant in your terminal and the one in your editor are working from the same notes instead of two different ideas of the project.
Where to find it
- All Features → Terminal agent detection
- Turn on or off
- Settings
What you get out of it
- Detection is what turns on every other terminal AI feature, so a recognised CLI immediately gains all three.
- Two assistants working on one project can share what Agentfly already remembers about it, instead of each starting from nothing.
- Recognition comes from the command you typed - nothing else about your machine is inspected.
- The offer appears once per agent per run, not every time you restart it.
How to use it, step by step
- Turn it on in AI settings; it is on by default.
- Start any agent CLI in Agentfly's terminal - claude, codex, gemini, grok, kimi, qwen, amp, goose, crush, droid, cursor-agent, aider, opencode or copilot.
- Agentfly recognises it from the command you typed and offers to share this project's memory with it.
- Choose Copy to put the connection command on your clipboard, then run it once if you want it.
- From then on that terminal can use automatic continuation, scheduled messages and Team.
Why this beats the usual way
Other editors treat the terminal as a dumb box that happens to be embedded. Agentfly notices what you started in it and makes the editor's own memory, scheduling and orchestration available to it - without a plugin per CLI.
Find it in Universal Search
Terminal agent detection · The assistant · recognise agent · detect cli · grok · kimi · codex · share memory with agent