Fimo Studio

Fimo Studio is the web app where your team manages a site without editing application code. Your coding agent builds the site, while Studio gives the rest of your team a place to edit content, review changes, and publish when ready.

​

What you can do

​

Find actions quickly

Press ⌘ K on macOS or Ctrl K on Windows and Linux to open Studio’s command palette. You can use it from anywhere in the app to:

• Move between organizations, projects, every Studio workspace, Preview pages, content types, agents, and settings pages.
• Search individual CMS pages and forms, schedules, webhooks, connections, and MCP servers by name.
• Search asset folders and code files instead of navigating through sidebars.
• Run actions for the page you’re viewing, such as editing or previewing the current page, managing an Inbox item, running or pausing a schedule, testing a webhook, inviting a member, or buying a domain.
• Open project history, invitations, publishing, documentation, and feedback.

The palette follows the same permissions and feature availability as the rest of Studio. Actions such as publishing still open their normal review or confirmation flow.

​

Organize previews with Environments

Open Project Settings → Environments to see how Branches map to deployment contexts. Production is live. Everything else is a preview. Environments are named places where your site runs, and Branches are matched to them. Production is the deployed snapshot visitors see and updates from the project’s configured source when you publish. Preview contains every Branch not assigned to another Environment. On Pro plans, project managers can create custom Environments using exact Branch names and one optional trailing pattern such as release/*. Unassigned Branches always fall back to Preview. See Branches for the Branch workflow.

​

Repair a blocked Preview

Some package managers block dependency install scripts until the project trusts each package. When this stops Preview, Studio shows the exact blocked packages. Project managers can approve that list and restart Preview in one action. Fimo updates the package manager’s project policy, records the change in project history, installs again, and returns to the regular Preview loader until the site is ready. Approving requires project management access. Without it the action stays in view, disabled, and says what access is missing, so everyone can still see what Preview is waiting on. Fix with Fimo stays available as an alternative for teammates who can use Studio chat. It asks the agent to review each blocked package, approve only the ones that clearly belong to this project and come from a source you trust, and never use a blanket approval. If a package is unexpected, ambiguous, or suspicious, the agent stops, explains the concern, and asks whether you want to remove it, replace it, or approve it explicitly. Fimo approves only the packages shown. If the project changed after Studio reported them, the approval is replaced by Refresh Preview, which loads the current list so you review what actually blocks the install now. Package managers without a package-level approval policy keep the manual repair option.

​

One project, two surfaces

Studio and the fimo CLI work on the same project. Developers and agents work through the command line; everyone else works in Studio. A change made in one shows up in the other, so the whole team stays in sync.

​

Agents and branches

The agents workspace and Branches are part of Studio for everyone, with nothing to enable. What you see follows your project role: every member can open Agents and switch Branches, while creating, merging, and deleting a Branch stays with project managers.

​

What’s next