Import from other agents
Bring into NoBreiniers what you already have in other coding agents on your Mac: connections, skills, hooks, subagents, model accounts and chats.
If you already use another coding agent on this Mac, you do not start from zero. NoBreiniers reads its files, changing nothing there, and you choose what comes in.
Before you start
- The other agent installed on this Mac, with its setup in your home folder.
Steps
- Open «Settings» (⌘,) › «Import».
- Under «On this Mac» you see what was found. Each tool is a group with what it holds: «Skills», «Helpers», «Connections», «Automatic steps», «Accounts» and «Chats of the last 30 days».
- Open a kind to see its items. Each one has its tick box and its state.
- Tick what you want to bring. Everything new that can come in is already ticked.
- Press «Import … items».
- Read «What came in»: how many came in, how many were already here, how many need one more step and how many could not come in, each with its reason.
If you install another tool later, press «Look again».
States
| State | It means |
|---|---|
| «New» | It is not in NoBreiniers yet. |
| «Already here» | You imported it before. Nothing is duplicated. |
| «Changed there» | It changed in its tool since you brought it. Importing it updates your copy. |
| «Cannot come in» | The app tells you why on the same row, in plain words, before you choose anything. |
Model accounts and helpers
- «Accounts». A model provider set up in the other tool comes in as an account of yours: if it is a provider the app already knows, it takes that one; any other comes in as one of the two formats, at the address its file gives. If its key is written in the file, the key goes to the vault and appears on no page. If it reads the key from a variable, or its tool keeps the key by itself, the account cannot come: «Its key is not written in the file … Add the account in Settings with your key.» A connection kind the app does not speak says «Its connection kind (“…”) is not one this app speaks: it could not come.», a file with no address says «The file gives no address for it.», and «Its own extra details did not come: an account here sends none.» The extra options its models sent in the body of their requests are kept with the account.
- Helpers. The other tool's helper files are read where they stand, also those of the folder that applies to the whole Mac (it comes first there, and the row says «It came from the settings of that tool for the whole Mac, which override a person's own there.»). A main agent of that tool is not a helper: «… is a main agent of that tool, not a helper: it did not come.» Its model and temperature are not used: «every helper works with the one model, at the effort you choose.»
- Not fetched from the internet, not brought: skills that the other tool fetches from an address («The skills at … are fetched by their tool from the internet. NoBreiniers does not fetch them; copy the skills to a folder and import again.») and its add-ons («… did not come: an add-on of that tool only runs inside that tool.»).
New skills in a tool you already brought
The app looks once a day by itself. If it finds new or changed skills in a tool you already brought skills from, a note appears at the top of the page: «…: … new and … changed skills since you brought yours. They are ticked below; press Import to bring them (each is checked first).» Press Import, or the x («Not now: hide this note until something else changes»). For a tool whose skills are read as ones from outside, the note says «They are not ticked: read each one's notes below, tick the ones you want and press Import (each is checked first).» and you tick the ones you want first. A skill that the review refuses is not counted as new.
What runs commands arrives turned off
Connections and hooks run commands on your Mac, so they come in turned off and you turn each one on.
- On the same page, scroll to «Turned off until you turn them on».
- Turn each server or hook on with its switch.
- If a server lacks something, it says so: «Give it a value for … before you turn it on.» or «Finish its setup (the gear) to sign in, then turn it on.» Press «Finish its setup».
- To take out a hook you do not want, press «Remove this hook from NoBreiniers».
Your chats
Imported chats show under «Chats you can open now» and in the sidebar, as ordinary chats with their tool's name beside the title. You can go on with the conversation here.
Skills from a public registry
Some tools install skills from a public registry where anyone can publish, and an installed skill sits among the ones you wrote. NoBreiniers reads every skill of such a tool as closely as a skill fetched from the internet: its text and every file in it are checked, and a skill that would pipe a download into a shell, decode and run hidden code, wipe your files or carry a program does not come in. Its row says why, and nothing else of it is kept.
- A skill the registry installed says so: «It was installed from the public skill registry of that tool, where anyone can publish.»
- A skill that carries scripts lists them: «It carries … scripts (…). They come as files; NoBreiniers never runs them when importing.» Read them before you let an agent use the skill.
- The review then says in plain words what the skill brings: the websites it talks to («It talks to these websites: …»), the keys it asks for («It asks for these keys: …»), how many notes it has, or «The skill review found nothing unusual: no scripts, no websites, no keys.»
- None of these skills is ticked for you, and the first-run card brings none of them. Read the notes of each row, tick the ones you want and press «Import». Until then it is not in NoBreiniers, and importing it runs nothing: its text is read as outside content when an agent loads it.
What stays in the other tool
- Memory notes. «Its memory notes are not brought here.» Bring them yourself in «Memory», with «Bring what another assistant knows about you» (Memory): you decide, note by note, what stays.
- Chats and scheduled jobs. When a tool keeps them in a database that also holds its sign-ins, NoBreiniers does not open it: «Its chats and scheduled jobs are kept in a database that also holds its sign-ins. NoBreiniers does not open it, so they did not come.»
- Main agents and add-ons. A main agent of that tool is named and does not come, and an automatic step written as a program of that tool says it is an add-on that only runs inside that tool.
- Connections. A tool's own list of allowed tools does not come: «Its list of allowed tools did not come.» Set it with the «Permissions» icon of the connection. Its own certificate settings do not come either: «Its own certificate settings did not come: it connects with the standard checks.»
- Accounts. A key the configuration names through a variable that the same configuration gives a value comes in as a key written in the file. A key that the tool keeps by itself, or reads from another place, does not: add the account in Settings with your key. A model server on this Mac needs no key.
- A broken configuration. If its configuration file cannot be read, the page says «Its configuration file cannot be read: it breaks at line …» and takes nothing from it; its skills still come. A file that the configuration includes and that is missing, is outside its folder or includes itself says «A file that the configuration includes could not be used …».
What the app takes care of
- It only reads. Nothing changes in the other tool.
- It never takes a sign-in. An account you sign in to in the other tool stays there.
- Keys go to the vault. A server's keys are kept encrypted, not in a file in plain sight.
- Yours is never replaced. If you already have something by that name, you see «Something named “…” is already here. Yours stays as it is.»
- Importing twice duplicates nothing.
- Nothing replaced is lost. When an update («Changed there») replaces your copy, the earlier skill goes to the Skills trash, where you can restore it, and an earlier helper's file goes to the Trash. If the new copy cannot be written, the earlier skill comes back as it was.
- Automatic steps in plain words. Each one says when it runs: «When you send a message», «Before a tool runs», «After a tool runs», «When a chat starts» and so on.
If something cannot come in
| Reason | What to do |
|---|---|
| «It passes a key inside the command that starts it, where any program on this Mac can read it…» | Move the key to a startup setting in its tool and import it again. |
| «It has no name or no description, so no agent would know when to use it.» | Complete it in its tool and import it again. |
| «This version of the tool keeps its chats in a way NoBreiniers does not read yet.» | The rest of that tool still comes in. |
| «This skill cannot be read here: it needs a name, a short description and its text.» | Complete it in its tool and import it again. |
| «This helper limits a tool to certain commands; that cannot be kept here.» | Give it the whole tool, or none, in its tool and import it again. |
| «This helper's file is longer than the app reads (about 64 KB).» | Shorten it in its tool and import it again. |
| «NoBreiniers has no matching moment for this automatic step, so it would never run.» | Nothing to do: that step has no equivalent here. |
| «It is not here any more.» | It was removed (for example, from the connections window) while the page was open: press «Look again». |
In the first-run setup
The first time you open the app, if another agent is on your Mac, «Setting up NoBreiniers» shows «Bring your setup from another agent». Press «Review and import» to reach this page, or «Not now».
