Skip to content

Comments

Import Augment (Augument) chat exports (Vibe Kanban)#1

Merged
abgyjaguo merged 1 commit intovk/d466-gh-3-support-impfrom
vk/3150-gh-3-support-imp
Jan 10, 2026
Merged

Import Augment (Augument) chat exports (Vibe Kanban)#1
abgyjaguo merged 1 commit intovk/d466-gh-3-support-impfrom
vk/3150-gh-3-support-imp

Conversation

@abgyjaguo
Copy link
Owner

@abgyjaguo abgyjaguo commented Jan 10, 2026

What

  • Added support for parsing Augment (Augument) JSON exports into the normalized { loglines: [...] } format used by the HTML renderer.
  • Added a representative fixture and test coverage for parsing + HTML generation.
  • Added black to the dev dependency group so uv run black . works in this repo.

Why

Issue #3 asks for importing Augment exports and rendering them correctly in the existing HTML transcript output. This enables using claude-code-transcripts json <export>.json on Augment exports the same way we already support Claude Code JSON/JSONL and Codex CLI JSONL.

Implementation details

  • parse_session_file() now:
    • returns existing normalized JSON unchanged when loglines is present
    • otherwise tries Augment export parsing before falling back to returning raw JSON
  • The Augment importer is tolerant of common export variants:
    • wrappers: messages, conversation.messages, conversations[].messages, chats[].messages, and data
    • role keys: role/sender/from/author with case-insensitive mapping to user or assistant
    • content keys: content/text/message/body, including list/dict shapes (best-effort text extraction)
    • timestamps: ISO strings or epoch seconds/milliseconds
  • Assistant message content is emitted as Claude-style content blocks ([{type:text,text: ...}]) so Markdown/code blocks render via the existing assistant rendering path.

Testing

  • tests/test_augment_format.py covers parsing the fixture and a couple common variant shapes, plus an end-to-end generate_html() sanity check.
  • uv run pytest

Acceptance criteria

  • Parsing works for real exports
  • Tests/fixtures added
  • HTML output renders correctly

This PR was written using Vibe Kanban

…e_transcripts/__init__.py:548` (see `_parse_augment_export_data` at `src/claude_code_transcripts/__init__.py:704`) so `claude-code-transcripts json <export>.json` produces normalized `loglines`.

- Added a real-ish fixture + tests + HTML check: `tests/sample_augment_export.json:1`, `tests/test_augment_format.py:1`.
- Added `black` to dev deps so `uv run black .` works: `pyproject.toml:35`.

Run:
- `uv run pytest`
- `uv run claude-code-transcripts json path/to/augment-export.json -o out --open`
@chatgpt-codex-connector
Copy link

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@abgyjaguo abgyjaguo merged commit 8e06800 into vk/d466-gh-3-support-imp Jan 10, 2026
@abgyjaguo abgyjaguo changed the title GH#3 Support importing Augment ("Augument") chat exports (vibe-kanban) Import Augment (Augument) chat exports (Vibe Kanban) Jan 10, 2026
abgyjaguo pushed a commit that referenced this pull request Jan 11, 2026
…Augment) (vibe-kanban 7894c989)

@cct_issue_binding
Issue: #4
Context:
- Track progress for #1/#2/#3

Acceptance criteria:
- [ ] Parsing works for real exports
- [ ] Tests/fixtures added
- [ ] HTML output renders correctly

@cct_new_format_support
@cct_tdd
@cct_dev_commands
@cct_pr_checklist
abgyjaguo pushed a commit that referenced this pull request Jan 11, 2026
@cct_issue_binding
Issue: #1
Context:
- Parse Cursor export format into normalized loglines

Acceptance criteria:
- [ ] Parsing works for real exports
- [ ] Tests/fixtures added
- [ ] HTML output renders correctly

@cct_new_format_support
@cct_tdd
@cct_dev_commands
@cct_pr_checklist
abgyjaguo pushed a commit that referenced this pull request Jan 11, 2026
…Augment) (vibe-kanban 7894c989)

@cct_issue_binding
Issue: #4
Context:
- Track progress for #1/#2/#3

Acceptance criteria:
- [ ] Parsing works for real exports
- [ ] Tests/fixtures added
- [ ] HTML output renders correctly

@cct_new_format_support
@cct_tdd
@cct_dev_commands
@cct_pr_checklist
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants