Start here
plgn is two things that work together: a workspace on the web where your marketing lives, and a plugin that lets the AI assistant in your terminal write into it. This page explains the shape of both, and points you at the page you actually need.
The two halves
Most marketing tools ask you to write inside them. plgn does the opposite. You write where you already work, a terminal, with an AI assistant, and plgn holds the result.
| The half | Where it lives | What it does |
|---|---|---|
| The workspace | useplgn.com, in a browser | Keeps your posts, pictures, topics and everything the system knows about your brand. Your team reviews here. Nothing publishes without a person. |
| The plugin | Claude Code, in your terminal | Adds twenty-seven commands starting with /plgn. They read your brand, write posts, make pictures, and save all of it into the workspace. |
You can use the workspace on its own. You cannot use the plugin on its own for anything that needs saving: seven of its commands work with no account at all, and the rest need a workspace to write into.
What you need before you start
- Claude Code, installed and working in your terminal. Everything else happens inside it.
- A website for your brand. Not required, but the plugin reads it to learn how you sound, and a description you type by hand gives a thinner result.
- A plgn workspace, for anything that saves. Free to create, and you can wait until after you have tried the free commands.
You never need an API key, a token or a password for plgn itself. If anything ever asks you to paste one into your terminal, something is wrong: sign-in happens in your browser, once.
Free commands and connected commands
The twenty-seven commands split into two groups, and the split is not about quality. It is about whether the result has anywhere to go.
| Free, seven commands | Connected, twenty commands | |
|---|---|---|
| Account needed | No | Yes |
| Writes posts in your voice | Yes | Yes |
| Where the result goes | Text in your terminal | Saved in your workspace |
| Checked against your banned words | No | Yes, on the server |
| Pictures made | No | Yes |
| Scheduled | No | Yes |
| Your team can review it | No | Yes, on the board |
A free command never reads or writes your workspace, signed in or not. When plgn is connected it reads websites and public posts through plgn's research tools (site_read, social_fetch, web_search), which cost a few points per read, so the server sees the addresses it reads and nothing else; without a connection it uses Claude Code's own web fetch. It cannot see your brand, so it works your voice out from your website and says so before it shows you anything. That guess is good enough to judge the tool by, and not good enough to publish thirty posts from.
Your first five minutes
- Install the pluginTwo lines inside Claude Code add the plugin and turn it on. The install page has them.
- Restart Claude CodeThis is the step people skip, and skipping it causes the single most common problem. Close it and open it again.
- Run a free command
/plgn demo https://yoursite.comgives you seven posts with no account and no sign-up. - Create a workspaceGo to useplgn.com and make one. This is where your posts and your brand will live.
- Run
/plgn setupYour browser opens once and asks you to approve access. Then the plugin reads your site and writes four things about your brand: how it sounds, who it talks to, what it sells, and words it refuses to use. - Write your first month
/plgn month "your subject" --dry-runshows the plan and writes nothing. Run it again without the flag when the plan looks right.
/plugin marketplace add PLGN-App/PLGN-CLAUDE /plugin install plgn ... restart Claude Code here ... /plgn demo https://yoursite.com /plgn setup /plgn month "Q3 launch" --dry-run
Which page you need
| If you want to | Read |
|---|---|
| Get it working, or fix it when it isn't | Install and connect |
| Know what a command does before you run it | Every command |
| Understand why it behaves the way it does | How it works |
| Fix posts that come out sounding wrong | What plgn knows |
| Predict its answers, or change how it writes | The skills |
| Know what runs when a month takes four minutes | The agents |
| Get faster, and avoid the expensive mistakes | Tips and recipes |
Read them in order if you have twenty minutes. Jump straight to the one you need if you do not. Each page stands on its own and names the others where they matter.
The words this documentation uses
Seven words appear on every page and each one means something narrower than it does in ordinary use. Learning them now saves you filing things in the wrong place later.
| Word | What it means here |
|---|---|
| Brand | One business you publish for. A workspace can hold several, an agency runs one per client. Each has its own voice, its own posts and its own banned words. |
| Post | One piece of copy for one platform. The same idea written for LinkedIn and for X is two posts, not one post in two places. |
| Draft | A saved post that is not going anywhere yet. Drafts are the safe state: nothing publishes from a draft, and a run that goes wrong leaves drafts you can delete. |
| Topic | A repeated argument the brand makes, not a category. "Migration stories" is a topic. "Educational" is not. It would fit any business in any market. |
| Offering | One thing the brand sells, saved as its own record with its benefits. Not a knowledge entry, and not the same as a post about it. |
| Campaign | One thing the brand is saying for a while, with a start and an end. Ramadan, a launch, a season. Posts inside it inherit its message and its rules, and stop inheriting them when it ends. |
| Point | What making a picture costs. Points come with your plan, and you can buy more. What one picture costs depends on the model it is made with, and every command that spends them states the cost before it spends anything. |