Troubleshooting

Most "problems" with the connector are actually the draft model working as designed — the agent needs your browser for structural editing. Here's what each situation means and the fix.

"Open your plan in the editor"

Your agent tried a draft edit (creating tasks, dependencies, planned dates, resource bookings, publishing) but no YAPL tab with the plan is open. Drafts live in your browser, not on the server — that's what keeps your published plan safe while you edit.

Fix: open yapl.app and open the plan. Then ask the agent to try again.

"The plan isn't on screen"

The tab is open, but you've navigated elsewhere in YAPL (say, the dashboard). Edits to a plan you can't see are refused on purpose. The agent can open it for you — "open Plan A" — or you can click into it yourself; the edit will go through right after.

The Agent Says It Made a Change, but You Don't See It

Two common causes:

• You're looking at the live plan; the change is in the draft (or vice versa). Status/progress/assignee/actual-date updates go to the live plan; structure and schedule edits go to the draft. Check the version selector.
• A stale tab. If YAPL was deployed since you last loaded the tab, hard-reload it (Ctrl/Cmd+Shift+R) and retry.

"No open tab" Right After You Opened One

The connection between YAPL's servers and your tab re-establishes within a few seconds of a page load or a network blip. Wait a moment and ask the agent to retry — the retry almost always lands.

The Agent's Tools Disappeared or Errors Mention Authorization

Your approval may have been revoked or expired. Reconnect: in your agent, remove and re-add the connector (or use its reconnect action), sign in, and approve again. See Connecting Your Agent.

My Agent Supports MCP but Can't Connect

The connector requires support for remote MCP servers (Streamable HTTP transport) with OAuth sign-in. Some clients only support local MCP servers or don't implement OAuth — check your agent's documentation for "remote MCP" or "custom connector" support. Any client meeting the standard connects without YAPL-side configuration.

"This workspace's plan does not include AI agent access"

The MCP Connector for AI Agents is a Professional and Trial feature, checked on every call. You'll see this if the workspace is on Basic, was downgraded, or its trial ended — even for agents connected earlier. Upgrading the workspace restores agent access immediately; there's nothing to reconnect.

Something Looks Wrong in the Data

The agent operates under your account with your permissions — it can't see other users' private data or bypass workspace boundaries. If numbers look off, check the same view in the app; the agent reads the same sources. Still stuck? Contact support.