SessionDock Developer Docs

Make your creative workflow programmable.

Authoritative guides, generated Local API reference, and practical patterns for local automation, scripts, launchers, and AI agents running alongside SessionDock.

Automation Examples

Practical patterns for launchers, assistants, metadata tools, and review workflows built on the Local API.

Automation examples

These examples are intentionally simple. The goal is to show reliable patterns that map well to launchers, shell tooling, and internal studio workflows.

Health and readiness check

Use this at startup in any automation client.

curl \
  -H "Authorization: Bearer $SESSIONDOCK_TOKEN" \
  "$SESSIONDOCK_BASE_URL/health"

Search the latest sessions

curl \
  -H "Authorization: Bearer $SESSIONDOCK_TOKEN" \
  "$SESSIONDOCK_BASE_URL/sessions?q=edm&recent=true&limit=10"

Update notes from a launcher action

curl \
  -X PUT \
  -H "Authorization: Bearer $SESSIONDOCK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "notes": "Send alt vocal print to client before 5 PM."
  }' \
  "$SESSIONDOCK_BASE_URL/sessions/session_123/notes"

Jump back into the desktop app

curl \
  -X POST \
  -H "Authorization: Bearer $SESSIONDOCK_TOKEN" \
  "$SESSIONDOCK_BASE_URL/sessions/session_123/focus"

Suggested client architecture

Read-only assistants

  • call /health at startup
  • use /sessions plus /preview
  • avoid any write surfaces

Full automation launchers

  • gate destructive actions behind effectiveMode
  • keep common write routes narrow and explicit
  • prefer field-specific endpoints when you only need notes or tags

Environment bootstrap

export SESSIONDOCK_BASE_URL="http://127.0.0.1:18432/api/v1"
export SESSIONDOCK_TOKEN="paste-your-token-here"