Modes
Starcat runs in one of four modes. Agent mode is the default.| Mode | What it does | Reach for it when |
|---|---|---|
| Agent | Takes action: runs tools, writes data, and dispatches projects. | You want Starcat to make the change, not just talk about it. |
| Plan | Read-only. Researches and drafts a plan for your approval before anything changes. | The task is non-trivial and you want to review the approach first. |
| Design | Iterates on visual designs and HTML preview mockups, without touching your data. | You’re mocking up a layout or exploring a look before building. |
| Chat | Answers questions without making any changes. | You just want to ask about your business, knowledge store, or apps. |
Agent Tiers
Next to the mode, you choose an agent tier. Starcat uses the same four tiers as the Developer Agent: Lite, Core, Plus, and Pro. They trade speed and cost against reasoning depth. Starcat defaults to Plus.- Lite or Core for quick questions, knowledge-store lookups, and light edits.
- Plus (the default) for most day-to-day work, including operating your apps and planning changes.
- Pro for complex orchestration across several projects, or anything that needs the deepest reasoning.
Conversation Settings
Chat visibility
Every conversation has a visibility you set from the chat’s settings:- Personal — only you can see the chat. This is the default.
- Shared with org — anyone in your organization can see it.
Allowing developer agents
By default Starcat answers questions and operates your existing apps. Building new apps and dispatching work to Developer Agents is gated behind a per-conversation toggle. Turn on developer agents for a chat when you want Starcat to coordinate changes across your projects. Operating your apps’ APIs doesn’t require this toggle; it’s controlled separately by each app’s Allow agent access setting.Related
Starcat Overview
What Starcat is and everything it can do
Best Practices
Tips for getting the most out of Starcat