Work across two projects
This takes you from “I have two projects” to “my agent moves work in both from one session” — about 10 minutes. You’ll need a personal account with at least two Plenar projects you can edit, and Claude Code connected with plenar connect.
Pin a default project
Open Settings → Profile in the dashboard, find Default project for AI agents, and pick the project you spend most of your time in. A fresh agent session targets this project unless you say otherwise — so you don’t retype the project name in every conversation.
Confirm the agent sees both
Ask the agent what it can reach:
The agent calls plenar_list_projects and marks your pinned default. If only one shows up, you don’t have membership on the other yet — check Settings → Members.
Create work in your default project
Talk to the agent normally — no project name needed, it uses your default:
It shows a New Plan, you say “apply”, done.
Switch focus to the other project
Name the project in conversation and the agent calls plenar_resolve_project to find the match:
Its reply names the project it resolved to, so you can correct it cheaply if it picked wrong.
Persist the switch (optional)
Shifting focus for the rest of the day? Say “Make Atlas SaaS my default.” The agent calls plenar_set_default_project, and your next session starts there.
Operate on a specific entity from either project
When you reference something by ID, the agent doesn’t need to know which project it’s in — Plenar derives that from the ID and checks your access first:
This works regardless of your default.
How the agent picks a project
For each call, Plenar resolves the target in order: an explicit project named in the request, then your pinned default. If neither lands a single answer — and you’re on an org key (pko_*) rather than a personal token — Plenar refuses rather than guessing, so automation never silently writes to the wrong project.
Common questions
Do I have to name the project every time? No. Pin a default and the agent uses it until you switch. Name a project only when you want a different one.
What if two projects have similar names? The agent resolves the closest match and names it in its reply. If it’s ambiguous, it asks before acting — confirm or correct.
How is this different from CI automation? A personal token has a default and can switch freely. Org keys for CI carry no default and require the project on every call — see CI with org keys.
What to do next
- CI with org keys — when automation outgrows a personal token.
- Connect Claude Code — the underlying integration setup.
- Track progress with Claude Code — the day-to-day agent workflow.