AmpCode Support

[TheOnlyWayUp]

A conversation plugin for Amp Code would be great.

[marcus]

Hey! 👋 I'm Kestrel, Marcus's AI assistant.

Noted! AmpCode adapter is on the radar alongside the Kiro request (#100). Marcus will weigh in on prioritization.

In the meantime — if you happen to know where AmpCode stores its conversation/session data locally, that'd be super helpful for scoping the adapter work. 🙏

[marcus]

Tracked on the Sidecar Roadmap 📋

[marcus]

AmpCode Adapter Research

Explored AmpCode's local data storage. Here's what I found:

Storage Location

~/.local/share/amp/
├── history.jsonl      # Command history (prompt + cwd per line)
├── secrets.json       # API key storage
├── session.json       # Current state (mode, last thread ID)
└── threads/           # Conversations as individual JSON files
    └── T-{uuid}.json

Thread Format

{
  "v": 13,
  "id": "T-019c40ba-daa0-7032-81c4-fdb800aabfae",
  "created": 1770612513442,
  "agentMode": "smart",
  "nextMessageId": 2,
  "messages": [
    {
      "role": "user",
      "messageId": 0,
      "content": [{ "type": "text", "text": "..." }],
      "userState": { "currentlyVisibleFiles": [] },
      "agentMode": "smart",
      "meta": { "sentAt": 1770612537003 }
    },
    {
      "role": "assistant",
      "messageId": 1,
      "content": [{ "type": "text", "text": "..." }, { "type": "tool_use", ... }]
    }
  ],
  "env": {
    "initial": {
      "trees": [{
        "displayName": "sidecar",
        "uri": "file:///Users/.../code/sidecar",
        "repository": { "type": "git", "url": "...", "ref": "refs/heads/main", "sha": "..." }
      }],
      "platform": { "os": "darwin", "client": "CLI", "clientVersion": "..." }
    }
  },
  "meta": {
    "traces": [{ "name": "agent", "id": "...", "startTime": "...", "endTime": "..." }]
  }
}

Key Observations

1. Simple file-based storage — Individual JSON files per thread in threads/ directory (no SQLite)
2. Project context in env.trees — Each thread knows its workspace via uri field
3. Agent modes — deep, free", rush, smartstored inagentMode`
4. Message structure — Similar to Claude/Anthropic format with role, content array, tool uses
5. Rich metadata — Traces include timing info, platform details, git repo state

Adapter Implementation Notes

• Watch ~/.local/share/amp/threads/ directory for new/modified files
• Use WatchScopeGlobal since it's user-level, not per-project
• Filter threads by env.initial.trees[].uri matching project root
• Extract title from first user message content
• Map agentMode to display badge (smart/rush/deep/free)
• Thread ID format: T-{uuid} — use as session ID

Resume Command

amp threads continue T-{uuid}

[marcus]

Hey @TheOnlyWayUp! Amp Code support has landed in v0.70.0 — along with Kiro CLI support as well.

The conversations plugin now auto-detects Amp threads from ~/.local/share/amp/threads/ and displays them alongside sessions from all the other agents. Token usage, tool calls, and project matching all work out of the box.

Thanks for the suggestion! Grab the latest with brew upgrade sidecar or the setup script.

[TheOnlyWayUp]

@marcus Good god, that was incredibly fast. Thank you, I'll give it a try!

[TheOnlyWayUp]

Tracked on the Sidecar Roadmap 📋

This project is not publicly visible, by the wya.