Install and connect
Five minutes from nothing to a working setup. This page also covers the two things that go wrong, how to keep the plugin current, and what to do when a command says it cannot reach your workspace.
Install the plugin
Both lines are typed inside Claude Code, not in your normal terminal. The first line tells Claude Code where the plugin lives. The second installs it.
/plugin marketplace add PLGN-App/PLGN-CLAUDE /plugin install plgn
Nothing runs on your machine except text. The plugin ships no scripts and no programs: it is a set of written instructions the assistant reads, plus a connection to plgn's server. It stores nothing locally and never touches a password.
Restart Claude Code, this step is required
Close Claude Code completely and open it again. Not a new tab, not a new session, the program itself.
This is worth remembering because it comes back. Every time you update the plugin, you restart again. A command that suddenly says you are not connected is almost always this, not a broken account.
Try it before you sign up
Seven commands work with no account, no sign-up and no keys. Run one now. It is the cheapest way to find out whether the writing is good enough for your brand.
/plgn help every command, in one list /plgn demo https://yoursite.com 7 posts written from your own site
/plgn demo reads your homepage and your about page, works out how you sound, picks three things you should be talking about, and writes seven complete posts across LinkedIn, X and Instagram. You can copy any one of them and publish it unchanged.
Create a workspace
Go to useplgn.com and create one. A workspace is where posts, topics, pictures and everything the system knows about your brand are stored. One workspace can hold several brands, which is how agencies run a client each.
A new workspace starts on a 14-day trial of the Brand plan -- one brand and enough room to see whether this fits how you work, no card needed. Once the trial ends, pick a paid plan from Settings → Plan to keep going. The limits your plan sets are listed on the page about what plgn knows.
Connect, once, in your browser
The first time you run a command that needs your workspace, your browser opens and asks you to approve access. Approve it once and you are done. The connection is remembered.
If your browser never opens, restart Claude Code and run any connected command again, such as /plgn queue. The approval prompt is triggered by the first command that needs it.
Teach it your brand
/plgn setup
This runs once per brand. It checks the connection, asks which brand you are setting up, reads your website, and drafts four things: how the brand sounds, who it talks to, what it sells, and the words it refuses to use.
It shows you all four in full before saving anything, what each one is and where it is kept is worth a look if you want to check them later. Read them properly. Everything written afterwards is built on top of them, and fixing a wrong voice now costs one minute, fixing it after thirty posts have inherited it costs an afternoon.
The one question worth thinking about
It will ask which words this brand refuses to use: competitor names, industry clichés, claims you cannot back up. Most people have never written that list down. It is worth two minutes, because the server enforces it: a post containing a banned word cannot be scheduled at all, whatever the assistant thinks.
Going further than setup
If you want the brand known properly, its look, its competitors, its topics and the lines it already reuses, run /plgn brandkit with your website afterwards. It reads your own published posts as well as your site and asks at most five questions, each with an answer already drafted for you.
Setting up pictures
Posts work without pictures. Pictures need two things set up in the dashboard, and neither blocks anything until you want one.
| What | Why it is needed | Without it |
|---|---|---|
| Image storage | A finished picture has to live somewhere your posts can point at. | Pictures can be made but have nowhere to be kept. |
| Image points | Making a picture costs points. They come with your plan, and you can buy more in the dashboard. | Pictures cannot be made; posts go out as text, which is fine. |
Both are set in the dashboard, never in the terminal. A command that finds one missing says what is missing and carries on with everything else rather than stopping.
Write your first month
/plgn month "your subject" --dry-run
--dry-run shows the plan, which topics, how many posts, how many pictures and what they cost, and writes nothing at all. It is the flag to use the first two or three times you run anything that writes in bulk.
When the plan looks right, run the same line without the flag, you will be asked to confirm once, and then it runs: posts written, checked, illustrated and scheduled.
Keeping the plugin up to date
Installed plugins do not update themselves. These two lines run in your normal terminal, not inside Claude Code.
claude plugin marketplace update plgn claude plugin update plgn
When something is not working
| What you see | What it means |
|---|---|
/plgn setup says you are not connected, but you are | You have not restarted Claude Code since installing or updating. This is the answer most of the time. |
| A command mentions an address that is not useplgn.com | Your installed copy is old. Update it, then restart. |
| Your browser never opens to approve access | Restart, then run any connected command such as /plgn queue. |
| A free command asks you to sign in | That is a bug. The seven free commands never need an account and never read or write a workspace. When plgn is connected they only read websites and public posts through its research tools. |
| A command says the brand has nothing saved | Run /plgn setup for that brand. Commands that write in your voice refuse to guess it when a real profile is one step away. |
| Posts are scheduled at strange hours | The brand has no timezone saved, or the wrong one. Fix it with /plgn knowledge, a time with no timezone lands wherever the server happens to think it is. |
The message you will see when the connection fails
Every connected command checks the connection before doing anything. When that check fails it names both possible causes, in order of likelihood, and stops. It never retries in a loop and never quietly does something smaller instead.
I can't reach your workspace. Two things cause this: You haven't restarted since installing or updating plgn. Restart Claude Code and run this again. You don't have a workspace yet. Create one at useplgn.com, then run this again.
When the check passes, nothing is printed. A check that succeeds is silent, so an empty pause before a result is normal.