How Google processes data
Necessary

Remember the site's theme and your choice in this window, in this browser's storage. Cloudflare's protective cookies protect the site from bots. Always on.

Google Analytics (Google Ireland Limited) counts visits and shows which sites and campaigns they come from. Cookies: _ga, _ga_*.

Google Ads (Google Ireland Limited) measures whether a visit from an ad ends with a click on the sign-up button. Cookies: _gcl_au and related.

List of cookiesHow Google processes data
Try 30 days free
How it worksTutorialsPricingFAQ
Sign in

Agents and consoles · step 6 of 8

Your consoles: several at once, Reconnect and Disconnect

On the Your consoles card you see each of your consoles in the organization: its name, its state and its term. There you also give a console a new connect command or disconnect it.

5 minutesreading time
Before you starta featureloom account, Claude Code or Codex connected with the app’s connect command
All the steps in one recording, narrated.
Contents

  1. Connect several consoles under one system account

    The default connection is one console for every folder on your system account: agents in each folder sign plans with the same name. The advanced connection gives one folder its own console, so you can tell agents apart. In the menu, open Integrations, press Connect console on the Your consoles card and choose Claude Code. In the window, press Show advanced and copy the command with Copy the folder’s connect command.

    The part A connect command for this folder only in the Connect Claude Code window: the command with --scope local, its secret covered, and the button Copy the folder’s connect command
    A connect command for one folder only

    Paste it in an ordinary system terminal, in the folder you run that console in, not inside the Claude Code window. The --scope local option saves the connection for that folder only.

    The folder’s connect command, in the console’s folder
    claude mcp remove --scope local featureloom; claude mcp add --scope local --transport http featureloom https://mcp.featureloom.com/mcp --header "Authorization: Bearer flc_…"

    Change the Server name in the console field when your account on this computer already has a featureloom server, for example one connected to another organization. The command then uses the new name.

  2. Give the console a name

    A new console gets its program’s name, for example Claude Code, and a second one of the same kind Claude Code 2. On the Your consoles card, press the pencil icon beside the name, type a name such as backend in the Console name field and press Save. The new name shows at once beside every signature of that console on the plans.

    A console’s row on the Your consoles card with backend in the Console name field and the Save button
    The name your signatures carry

  3. Check its state and term

    Each row says whether the console is live, expired or disconnected, and when it was last used. A connect command with a secret works for 90 days from its issue, and lapses sooner when the console does no work for 14 days. Under the state you see whichever date comes first: Expires or Lapses without use after.

    The Your consoles card with two consoles, backend and Claude Code: their state Live, their term and their use
    The state, term and use of each console

    7 days before the term ends, featureloom reminds you by email.

  4. Give the console a new connect command: Reconnect

    When you lose the connect command, when it expires or when it ends up somewhere it should not be, press Reconnect in the console’s row. If the window first shows Confirm it’s you, confirm the way you sign in. The window gives you a new connect command for the same console, and the old one stops working at once. Paste the new one as you did the first: the console stays the same, with its signatures.

    The row of the console backend with the Reconnect and Disconnect buttons
    A new connect command for the same console

    A console connected by signing in through the browser renews by signing in again: type /mcp in it and sign in once more.

  5. Disconnect or delete a console

    Disconnect cuts the console off at once, after you confirm. The plans keep a record of what it did, but a disconnected console cannot be connected again: when you need it once more, connect a new one. Only a console that has done nothing yet has the bin icon beside it: press it to delete the console entirely.

    The confirmation in a console’s row: Disconnect backend? It stops working at once; its signatures stay.
    Disconnecting keeps the record of its work

Good to know

  • You have up to 10 live consoles in one organization. When you connect an eleventh, featureloom disconnects the one you haven’t used for the longest time.
  • Always start a console with a folder’s connect command in that same folder. Started in another one, a subfolder included, it does not see the connection.
  • The connect command holds your secret: never paste it into a chat or a repository. A console acts with the rights of the person it belongs to, so every person connects their own consoles.
  • You show your disconnected and expired consoles on the Your consoles card with Show disconnected and expired.
  • Which networks your consoles connected from in the last 90 days, you can check on the Your account screen, in its Console workplaces part. The organization’s administrator does not see it.

Updated: November 5, 2026

Next

An automation: an account for jobs on a server, with its own key

Your consoles are in order: give the jobs no person runs an account of the organization’s own, with a key.

See the tutorial