Projects and the library
Your organization runs its instances in one namespace, under one quota. Projects and the library organize what runs in it: which instances belong together, and which skills and MCP servers each of them starts with.
Projects
A project groups instances, and has a library, network rules and listeners of its own. The
Projects page makes them, up to 3 on the free plan and 10 on
an invited one, and only an owner or admin does. A name is lowercase letters, digits and -, and not main, default
or portal. New instance has a project box when you have any, the instance list can be filtered by project, and an
instance stays in the project it was made in. A project is not a limit: its instances share your quota, and count
against your running instances, objects and compute like any other. A project is deleted from its page once no instance
is in it, with its library, rules and listeners.
The library
The library is the skills and MCP servers that every instance made in a scope starts with, for an agent that reads them (Claude Code). It has three levels, the widest first:
- your organization's, on the Skills page, for every instance;
- a project's, on the same page with the project picked, for the instances of that project as well;
- the instance's own, on New instance (Deploy from git).
An entry of the same name at a later level replaces the earlier one, and a skill of that name inside the repository itself wins over all of them: the organization's skills are defaults, not policy, since the agent can change the files it works with.
A skill is a GitHub or GitLab repository with a SKILL.md at its root, or a repository that holds several, in
skills/NAME or .claude/skills/NAME: the page lists what it finds in a public GitHub repository, and you pick which
to add. A private repository or a GitLab one is taken as it is, and a wrong one shows as an error in the instance's
status. An MCP server is a name and either the https URL of a remote server or a command that starts one in the
instance. The host of a remote server has to be one your instances may reach (Network rules), and its
calls then go through poema, so a rule there can limit its tools and add a token. A library holds 30 entries a scope, and
an instance 20 skills and 10 servers in all.
A snapshot, and Update
An instance takes the library when it is made and keeps it: a change reaches the instances made after it, and the ones that run go on with what they had. The instance's page says so when the library has changed since. Its Update button makes the instance again from the library as it is now: the skills and servers of its own are kept, the ones it took from the library are replaced, and, as the instance is recreated, its files are deleted. An instance made before the library existed has neither the note nor the button.
What limits an agent's tools
Only a remote MCP server is limited for certain: it is reached through poema, where the host's rule allows the tools it
names and refuses the others. For the servers an instance runs itself and for the agent's own tools (Bash, WebFetch and
so on), New instance's Agent permissions turn off what Claude Code may do (run shell commands, change files, use the
web, start sub-agents, schedule work), or a preset of them such as Read-only, and under Individual tools any one of its
tools or an MCP server's (mcp__server__tool). Claude Code drops those when it starts. That is advisory:
another agent, or a shell in the instance, is not limited by it, and removing WebFetch does not stop network access,
which the hosts of Network do. The instance's page lists the MCP servers it has and, on a click,
the tools each offers; listing starts the servers, so it needs the instance to be running.
Activity
The Activity page lists what you changed and what happened to your instances, newest first.