Native vs Connected
Overview
Section titled “Overview”GrowthOS always owns planning: Idea Lab, PRDs, UX Spec, the backlog, and sprint plans live in GrowthOS no matter how you execute. The choice is where day-to-day task tracking happens once a sprint starts.
Native keeps sprint boards and My Tasks inside GrowthOS. Everyone opens one app for planning and doing the work; status updates on the board roll into reports and Today.
Connected pushes issues to Linear, Jira, GitLab, Asana, or ClickUp and reads status back. It is plan-gated (integrations.connected), not a separate product SKU. A third path is coding agents: they work Native tickets over MCP and must not overwrite Connected synced status.
What you can do here
Section titled “What you can do here”- Keep planning artifacts as the system of record in Native, Connected, or agent execution.
- Connect an external tracker from Organization → Integrations when your plan includes Connected.
- Connect a coding agent from Settings → API Keys & Agents or the sprint board.
- Run Native immediately with zero setup while you decide on Connected later.
When to use
Section titled “When to use”- Choose Native for teams that want one workspace for planning and execution.
- Choose Connected when engineering already lives in an external tracker and will not switch boards.
- Add a coding agent when you want Cursor or Claude to pick up sprint tasks without leaving the repo.
Prerequisites
Section titled “Prerequisites”- Owner or Admin role to change organization-level integration settings.
- For Connected: a plan that includes
integrations.connectedand OAuth credentials for the target tool. - For agents: a gos_ API key (Free includes 1 MCP handoff; Pro and above are unlimited).
Where to find it
Section titled “Where to find it”- Organization → Integrations (
/org/integrations) for Native vs Connected providers. - Settings → Security → API Keys & Agents, or Connect coding agent on a sprint board.
Step-by-step
Section titled “Step-by-step”- Decide whether execution stays in GrowthOS (Native), moves to a tracker (Connected), or uses a coding agent.
- Open Organization → Integrations to see which providers your plan allows.
- Plan as usual in Idea Lab and Product Backlog regardless of mode.
- Run sprint planning, then track Native on the GrowthOS board or push to the partner tool.
- If using an agent, mint a gos_ key and follow the sprint loop — one task at a time.
- On Connected projects, do not let an agent overwrite tracker-synced status.
What success looks like
Section titled “What success looks like”- Every teammate knows whether to update status in GrowthOS, the external tracker, or via agent handoff.
- Planning artifacts stay accurate regardless of execution mode.
- You can explain Native vs Connected vs agent to a new hire in under a minute.
Tips & best practices
Section titled “Tips & best practices”- Start Native by default; it is the fastest path to a working sprint with zero setup.
- Coding agents complement Native; they are not a replacement for Connected trackers.
- Document per-project mode in the project description so new members are not confused.
Common mistakes
Section titled “Common mistakes”- Assuming Connected is on every plan; it is gated by
integrations.connected. - Letting an agent change status on a Connected-synced task (
TASK_SYNCED_READ_ONLY). - Blocking a first-week walkthrough on Connected setup when Native would unblock the team today.