# Set up your agent

> Connect your agent and verify its first tool call.

Source: https://docs.synkro.sh/onboarding/coding-agents

Synkro is in public preview. If your agent isn't listed here, email [team@synkro.sh](mailto:team@synkro.sh) and we can enable it for you or build a custom integration.

Run `synkro install` after installing your agent. Start a new session in a repository with `synkro.toml` and `synkro.lock`, then [verify a new decision](/onboarding/verify-events).

## Claude Code

Complete Claude Code's sign-in and first-run setup, including its interactive prompts after `claude auth login`.

1. Exit the old session and start a new one.
2. Look for the `[⧉ synkro]` startup notice.
3. Check `configuredHarnesses.claude_code` in `synkro status --json`.
4. Follow [Verify a decision](/onboarding/verify-events).

Synkro also sets a shutdown-hook timeout in `~/.claude/settings.json` when you have not set one yourself. This lets the SessionEnd hook finish. Existing overrides are preserved. See [SessionEnd hook cancelled](/troubleshooting#claude-reports-sessionend-hook-cancelled).

## Codex

1. Start a new session and send a prompt.
2. Review and trust Synkro's current hooks in Codex's Hooks settings. In the terminal interface, use `/hooks`.
3. Check that the Synkro MCP server is enabled. In the terminal interface, use `/mcp`.
4. Run `synkro status --json`. Check `configuredHarnesses.codex`, `configuredMcp.codex`, and `plugins.codex.toolBoundaryReady`.
5. Follow [Verify a decision](/onboarding/verify-events).

If `plugins.codex.hooksTrusted` is `null`, confirm hook trust in Codex's Hooks settings. See [OpenAI's hook documentation](https://learn.chatgpt.com/docs/hooks).

Synkro configures Codex to use execution paths that support its hooks, with Code Mode disabled. Connected-tool access may need owner approval; see [Synkro MCP](/reference/supported-agents#codex-also-uses-synkro-mcp).

## Google Antigravity

Start a new session, check `configuredHarnesses.antigravity`, then [verify a decision](/onboarding/verify-events). No startup notice is expected for Antigravity.

## Cursor

Start a new Agent session and check `configuredHarnesses.cursor`. Use Cursor's plugin settings for enabled or trusted states that Synkro cannot report. Then [verify a decision](/onboarding/verify-events).

If a new decision does not appear, follow [Troubleshooting](/troubleshooting#no-new-decision-appears). A `null` status means the setting could not be reported; check it in the agent's interface.