Work with Patchnet from your AI tool

Get the most from a connected AI tool: orient it once, then ask it to find, file, and update records in your projects.

When to use this

You have connected Claude Code, Codex, or another MCP client to Patchnet Projects, and you want your agent to do real work in your projects.

Before you begin

• A connected tool. See Connect your AI tool.
• Access to at least one project where you are a Writer or higher, if you want the agent to create or change records.

Orient your agent

Paste this into the first conversation after you connect. It tells the agent how Patchnet works and checks the connection from start to finish.

You are connected to Patchnet Projects.

First, call patchnet_help with topic "getting-started", then call
patchnet_list_projects.

Project path rules:
- my/private/* projects are my personal workspace.
- org/shared/* projects are shared company projects.
- Use project paths when you talk to me.

Before creating or updating records:
1. Pick the project from patchnet_list_projects.
2. Call patchnet_schema for that project to see its record types.
3. Look for existing records first, so you update instead of duplicating.

Write one record at a time and wait for each result before the next.

If anything fails, tell me the exact error and what you would try next.

Your agent should reply with the projects you can access. Some tools, such as Claude Code, can save instructions like these so you do not have to paste them each time.

Ask for real work

Name the project and say what you want as a result. For example:

• "Summarize the open tasks in org/shared/client-onboarding, grouped by owner."
• "In my journal, record a note about today's call with the design team."
• "Record a decision in org/shared/ops: we move the weekly review to Thursdays. Include why."
• "Find the decision about welcome packs and update it: the deadline is now three business days."
• "How many cases in org/shared/support are still open, by status?"

Good habits

• Name the project. It saves a lookup and prevents records from landing in the wrong place.
• Prefer updates over new records. Ask the agent to check for an existing record before it creates one.
• Keep records self-contained. A record should make sense to a teammate who never saw the chat.
• Check the result. Open the record in the browser the first few times to confirm it looks right.
• Keep secrets out. Do not paste passwords, keys, or customer data that a project's members should not see.

If something fails

• The agent cannot find a project — ask it to run patchnet_list_projects and check the exact path. You may not have access.
• The agent cannot write — your role on that project is Reader. Ask a project admin for Writer access.
• A record is rejected — the project's record type requires a field the agent left out, or a value that is not allowed. Ask the agent to check the project's record types with patchnet_schema and try again.
• You hit a limit — the error says how long to wait before retrying. See Limits.

See also

• Design a project with your agent
• MCP tools reference