Agents

An agent in Neo is a Claude Code (or Codex) instance running on one of your servers, shown in the interface as a separate “employee”: its own name, card, connections and state.

Creating an agent

Agents → “New agent”: a name (any language — the technical name is generated for you) and the server it will run on. You need at least one verified server; if you don’t have one yet, you can add it right from this same screen.

You can also:

• attach the agent to a project — it then gets the project’s shared context (who you are, what you do, who your clients are);
• give it isolated memory, or share memory with another agent already running on the same server.

Once created, the agent appears right away under Sessions.

The agent’s browser

You can turn on a browser of the agent’s own (agent card → “Browser sessions”). It keeps a persistent profile: a sign-in done once is kept and reused automatically from then on.

If the agent needs to sign in somewhere under your own personal account, it never types the password itself and never asks you for it in chat — it sends a sign-in request, which you see and approve under Sessions (see Sessions).

Telegram topics

Agent card → “Telegram topics”: an agent can run a whole Telegram group through its own topics, each one a separate conversation with its own context — /new in a topic restarts it, closing a topic archives it. All of an agent’s topics share its long-term memory. A group is bound with a code shown on the agent’s card (/bind <code> sent in the group) — a group the bot was simply added to gets nothing until the code is sent. The bot needs to be a group admin, or have privacy mode turned off in @BotFather — otherwise it won’t see messages inside topics.

If Neo is temporarily unreachable

The browser and Telegram topics run on a license that keeps working for up to a week even if Neo doesn’t answer — a short outage on either side won’t turn these features off.