Create a workspace key, fetch the connection kit, load recent memory, then save a checkpoint when the session ends.
startup calls: bootstrap, recent, tools, context
hosted MCP tools available through one endpoint
starter skills downloadable as JSON or Markdown
Use a separate workspace API key for each agent, worker, or integration so usage and revocation stay clean.
`/connect` returns endpoint URLs, MCP settings, starter skills, and the startup calls a client should run.
Start with recent memory, then ask `recall_context` for compact task-specific state before making changes.
End with `session_checkpoint` or `session_handoff` so the next agent session starts with the right state.
This is the recommended order for a new agent session.
Load endpoint URLs, tool discovery, starter skills, and auth shape.
Fetch recent memory and compact task context before changing files.
Use direct routes for search/write and the MCP bridge for higher-level tools.
Save `session_checkpoint` or `session_handoff` so the next session resumes cleanly.
Replace `{slug}` with the workspace slug and authenticate with a workspace API key.
Keep this small. The goal is enough state to start, not a giant prompt dump.
Ask the hosted bridge for task-specific context after bootstrapping.
A checkpoint is cheap and makes the next session faster.