claude-converter 1.0.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- claude_converter-1.0.0/LICENSE +201 -0
- claude_converter-1.0.0/PKG-INFO +282 -0
- claude_converter-1.0.0/README.md +254 -0
- claude_converter-1.0.0/claude_converter/__init__.py +1 -0
- claude_converter-1.0.0/claude_converter/converter.py +394 -0
- claude_converter-1.0.0/claude_converter.egg-info/PKG-INFO +282 -0
- claude_converter-1.0.0/claude_converter.egg-info/SOURCES.txt +10 -0
- claude_converter-1.0.0/claude_converter.egg-info/dependency_links.txt +1 -0
- claude_converter-1.0.0/claude_converter.egg-info/requires.txt +6 -0
- claude_converter-1.0.0/claude_converter.egg-info/top_level.txt +1 -0
- claude_converter-1.0.0/pyproject.toml +48 -0
- claude_converter-1.0.0/setup.cfg +4 -0
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2025 Aquiles-ai
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
@@ -0,0 +1,282 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: claude-converter
|
|
3
|
+
Version: 1.0.0
|
|
4
|
+
Summary: A zero-dependency Python module for inspecting and converting Claude Code session files '.jsonl' into the 'messages' format expected by Hugging Face Transformers.
|
|
5
|
+
Author-email: Fredy Rivera <fredyriveraacevedo13@gmail.com>
|
|
6
|
+
License: Apache License 2.0
|
|
7
|
+
Project-URL: Homepage, https://github.com/FredyRivera-dev/claude_converter
|
|
8
|
+
Project-URL: Issues, https://github.com/FredyRivera-dev/claude_converter/issues
|
|
9
|
+
Keywords: ai,claude,transformers
|
|
10
|
+
Classifier: Development Status :: 4 - Beta
|
|
11
|
+
Classifier: Programming Language :: Python :: 3
|
|
12
|
+
Classifier: Programming Language :: Python :: 3.8
|
|
13
|
+
Classifier: Programming Language :: Python :: 3.9
|
|
14
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
15
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
16
|
+
Classifier: Operating System :: OS Independent
|
|
17
|
+
Classifier: Environment :: Web Environment
|
|
18
|
+
Classifier: Topic :: Software Development :: Build Tools
|
|
19
|
+
Requires-Python: >=3.8
|
|
20
|
+
Description-Content-Type: text/markdown
|
|
21
|
+
License-File: LICENSE
|
|
22
|
+
Provides-Extra: dev
|
|
23
|
+
Requires-Dist: pytest; extra == "dev"
|
|
24
|
+
Requires-Dist: black; extra == "dev"
|
|
25
|
+
Requires-Dist: isort; extra == "dev"
|
|
26
|
+
Requires-Dist: mypy; extra == "dev"
|
|
27
|
+
Dynamic: license-file
|
|
28
|
+
|
|
29
|
+
# claude_converter
|
|
30
|
+
|
|
31
|
+
A zero-dependency Python module for inspecting and converting [Claude Code](https://www.anthropic.com/claude-code) session files (`.jsonl`) into the `messages` format expected by Hugging Face Transformers.
|
|
32
|
+
|
|
33
|
+
Claude Code stores every session as a JSONL file on disk under `~/.claude/projects/<encoded-project-path>/<session-uuid>.jsonl`. Each line is a JSON record containing the full message history — user prompts, assistant responses, tool calls, tool results, and extended thinking blocks. This module parses that format and flattens it into the simple `[{"role": ..., "content": ...}]` list that `tokenizer.apply_chat_template()` consumes directly.
|
|
34
|
+
|
|
35
|
+
## Why this exists
|
|
36
|
+
|
|
37
|
+
The conversion pipeline has two stages that are often conflated:
|
|
38
|
+
|
|
39
|
+
```
|
|
40
|
+
Claude Code JSONL → [claude_converter] → messages[] → apply_chat_template() → tokens
|
|
41
|
+
(this module) (transformers handles this)
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
`apply_chat_template()` handles stage 2 (turning a `messages` list into model-specific token sequences), but it knows nothing about Claude Code's JSONL format. This module handles stage 1.
|
|
45
|
+
|
|
46
|
+
## Installation
|
|
47
|
+
|
|
48
|
+
```bash
|
|
49
|
+
uv pip install claude-converter
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
## Quick start
|
|
53
|
+
|
|
54
|
+
```python
|
|
55
|
+
from claude_converter import session_to_messages
|
|
56
|
+
|
|
57
|
+
messages = session_to_messages("path/to/session.jsonl")
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
`messages` is ready for `apply_chat_template()`.
|
|
61
|
+
|
|
62
|
+
## API reference
|
|
63
|
+
|
|
64
|
+
### `load_session(path)`
|
|
65
|
+
|
|
66
|
+
Loads a Claude Code `.jsonl` file and returns the raw list of record dicts — one per line.
|
|
67
|
+
|
|
68
|
+
```python
|
|
69
|
+
from claude_converter import load_session
|
|
70
|
+
|
|
71
|
+
records = load_session("session.jsonl")
|
|
72
|
+
# [{"type": "user", "uuid": "...", "message": {...}, ...}, ...]
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
Raises `FileNotFoundError` if the file doesn't exist, `ValueError` if the extension is not `.jsonl` or `.json`, or if the file contains no valid records.
|
|
76
|
+
|
|
77
|
+
### `session_to_messages(path, output=None)`
|
|
78
|
+
|
|
79
|
+
Loads a session and converts it to a `messages` list in one call. Optionally saves the result to a JSON file.
|
|
80
|
+
|
|
81
|
+
```python
|
|
82
|
+
from claude_converter import session_to_messages
|
|
83
|
+
|
|
84
|
+
# In-memory only
|
|
85
|
+
messages = session_to_messages("session.jsonl")
|
|
86
|
+
|
|
87
|
+
# Save to disk too
|
|
88
|
+
messages = session_to_messages("session.jsonl", output="messages.json")
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
Returns `list[{"role": str, "content": str}]`. Content blocks (`tool_use`, `tool_result`, `thinking`, `text`) are flattened to plain text using XML-style tags so the conversation structure is preserved.
|
|
92
|
+
|
|
93
|
+
### `records_to_messages(records)`
|
|
94
|
+
|
|
95
|
+
Converts an already-loaded list of records into the messages format. Useful when you want to load once and run multiple transformations without re-reading the file.
|
|
96
|
+
|
|
97
|
+
```python
|
|
98
|
+
from claude_converter import load_session, records_to_messages
|
|
99
|
+
|
|
100
|
+
records = load_session("session.jsonl")
|
|
101
|
+
messages = records_to_messages(records)
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
### `inspect_session(path, show_flow=False, show_blocks=False, show_raw=False)`
|
|
105
|
+
|
|
106
|
+
Prints a color-coded report of a session: record type counts, content block breakdown by role, and token usage totals. The conversation flow is optional and off by default.
|
|
107
|
+
|
|
108
|
+
```python
|
|
109
|
+
from claude_converter import inspect_session
|
|
110
|
+
|
|
111
|
+
# Stats only (default)
|
|
112
|
+
inspect_session("session.jsonl")
|
|
113
|
+
|
|
114
|
+
# Stats + timestamped conversation flow
|
|
115
|
+
inspect_session("session.jsonl", show_flow=True)
|
|
116
|
+
|
|
117
|
+
# Flow + content of every block inline
|
|
118
|
+
inspect_session("session.jsonl", show_flow=True, show_blocks=True)
|
|
119
|
+
|
|
120
|
+
# Full report: flow, blocks, and raw record structure examples
|
|
121
|
+
inspect_session("session.jsonl", show_flow=True, show_blocks=True, show_raw=True)
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
Example output (default):
|
|
125
|
+
|
|
126
|
+
```
|
|
127
|
+
══════════════════════════════════════════════════════════════════════
|
|
128
|
+
CLAUDE CODE SESSION INSPECTOR
|
|
129
|
+
══════════════════════════════════════════════════════════════════════
|
|
130
|
+
File : session.jsonl
|
|
131
|
+
Size : 3.6 KB
|
|
132
|
+
Lines : 9
|
|
133
|
+
Session : abc-123
|
|
134
|
+
CWD : /home/user/myproject
|
|
135
|
+
Branch : main
|
|
136
|
+
══════════════════════════════════════════════════════════════════════
|
|
137
|
+
|
|
138
|
+
RECORD TYPES
|
|
139
|
+
user 4 ████
|
|
140
|
+
assistant 4 ████
|
|
141
|
+
system 1 █
|
|
142
|
+
|
|
143
|
+
CONTENT BLOCKS (by record type)
|
|
144
|
+
assistant
|
|
145
|
+
· text 3
|
|
146
|
+
· tool_use 2
|
|
147
|
+
· thinking 1
|
|
148
|
+
user
|
|
149
|
+
· text 2
|
|
150
|
+
· tool_result 2
|
|
151
|
+
|
|
152
|
+
TOKEN USAGE
|
|
153
|
+
Input : 2,617
|
|
154
|
+
Output : 147
|
|
155
|
+
Cache read : 1,700
|
|
156
|
+
Cache write : 482
|
|
157
|
+
Total : 2,764
|
|
158
|
+
```
|
|
159
|
+
|
|
160
|
+
## Using the output with Transformers
|
|
161
|
+
|
|
162
|
+
```python
|
|
163
|
+
from transformers import AutoTokenizer, AutoModelForCausalLM
|
|
164
|
+
from claude_converter import session_to_messages
|
|
165
|
+
|
|
166
|
+
MODEL_ID = "your-model-id"
|
|
167
|
+
|
|
168
|
+
messages = session_to_messages("session.jsonl", output="messages.json")
|
|
169
|
+
tokenizer = AutoTokenizer.from_pretrained(MODEL_ID)
|
|
170
|
+
|
|
171
|
+
tokens = tokenizer.apply_chat_template(
|
|
172
|
+
messages,
|
|
173
|
+
tokenize=True,
|
|
174
|
+
add_generation_prompt=True,
|
|
175
|
+
return_dict=True,
|
|
176
|
+
return_tensors="pt",
|
|
177
|
+
)
|
|
178
|
+
```
|
|
179
|
+
|
|
180
|
+
## Fine-tuning local models
|
|
181
|
+
|
|
182
|
+
Claude Code sessions are a natural source of training data: they capture
|
|
183
|
+
real coding conversations (tool calls, reasoning traces, multi-turn edits)
|
|
184
|
+
in a format that maps directly to the `messages` list expected by every major
|
|
185
|
+
fine-tuning framework.
|
|
186
|
+
|
|
187
|
+
### Preprocessing recommendations
|
|
188
|
+
|
|
189
|
+
Before training, filter the messages list for your target model:
|
|
190
|
+
|
|
191
|
+
- **Strip tool blocks**: most local models don't understand `<tool_use>` /
|
|
192
|
+
`<tool_result>` tags. Remove or replace them unless you are training a
|
|
193
|
+
tool-calling model.
|
|
194
|
+
- **Strip thinking blocks**: `<thinking>` blocks leak chain-of-thought that
|
|
195
|
+
may not generalize. Keep them only if you are distilling reasoning behavior.
|
|
196
|
+
- **Drop short or empty turns**: single-word assistant replies and empty
|
|
197
|
+
user turns add noise.
|
|
198
|
+
|
|
199
|
+
```python
|
|
200
|
+
def clean_messages(messages, keep_tool_calls=False, keep_thinking=False):
|
|
201
|
+
import re
|
|
202
|
+
cleaned = []
|
|
203
|
+
for msg in messages:
|
|
204
|
+
content = msg["content"]
|
|
205
|
+
if not keep_thinking:
|
|
206
|
+
content = re.sub(r"<thinking>.*?</thinking>", "", content, flags=re.DOTALL)
|
|
207
|
+
if not keep_tool_calls:
|
|
208
|
+
content = re.sub(r"<tool_use.*?>.*?</tool_use>", "", content, flags=re.DOTALL)
|
|
209
|
+
content = re.sub(r"<tool_result>.*?</tool_result>", "", content, flags=re.DOTALL)
|
|
210
|
+
content = content.strip()
|
|
211
|
+
if content:
|
|
212
|
+
cleaned.append({"role": msg["role"], "content": content})
|
|
213
|
+
return cleaned
|
|
214
|
+
```
|
|
215
|
+
|
|
216
|
+
### TRL / SFTTrainer example
|
|
217
|
+
|
|
218
|
+
```python
|
|
219
|
+
from datasets import Dataset
|
|
220
|
+
from trl import SFTTrainer, SFTConfig
|
|
221
|
+
from transformers import AutoTokenizer, AutoModelForCausalLM
|
|
222
|
+
from claude_converter import session_to_messages
|
|
223
|
+
import glob
|
|
224
|
+
|
|
225
|
+
MODEL_ID = "your-model-id"
|
|
226
|
+
|
|
227
|
+
all_messages = []
|
|
228
|
+
for path in glob.glob("~/.claude/projects/**/*.jsonl", recursive=True):
|
|
229
|
+
msgs = session_to_messages(path)
|
|
230
|
+
msgs = clean_messages(msgs)
|
|
231
|
+
if len(msgs) >= 2:
|
|
232
|
+
all_messages.append({"messages": msgs})
|
|
233
|
+
|
|
234
|
+
tokenizer = AutoTokenizer.from_pretrained(MODEL_ID)
|
|
235
|
+
model = AutoModelForCausalLM.from_pretrained(MODEL_ID)
|
|
236
|
+
dataset = Dataset.from_list(all_messages)
|
|
237
|
+
|
|
238
|
+
trainer = SFTTrainer(
|
|
239
|
+
model=model,
|
|
240
|
+
args=SFTConfig(output_dir="./output", max_seq_length=4096),
|
|
241
|
+
train_dataset=dataset,
|
|
242
|
+
processing_class=tokenizer,
|
|
243
|
+
)
|
|
244
|
+
trainer.train()
|
|
245
|
+
```
|
|
246
|
+
|
|
247
|
+
### Axolotl / LLaMA-Factory
|
|
248
|
+
|
|
249
|
+
Both frameworks accept a `sharegpt` format, which is structurally identical to
|
|
250
|
+
the `messages` list this module produces. Save the cleaned messages list with
|
|
251
|
+
`output="messages.json"` and point your framework config at that file.
|
|
252
|
+
|
|
253
|
+
## Content block mapping
|
|
254
|
+
|
|
255
|
+
Claude Code sessions contain several block types that have no direct equivalent in the Transformers `messages` format. This module flattens them as follows:
|
|
256
|
+
|
|
257
|
+
| Claude Code block | Flattened as |
|
|
258
|
+
|---|---|
|
|
259
|
+
| `text` | plain text, as-is |
|
|
260
|
+
| `thinking` | `<thinking>...</thinking>` |
|
|
261
|
+
| `tool_use` | `<tool_use name='...'>{input JSON}</tool_use>` |
|
|
262
|
+
| `tool_result` | `<tool_result>...</tool_result>` |
|
|
263
|
+
| `system` records | skipped (not included in messages output) |
|
|
264
|
+
|
|
265
|
+
Records with an empty content string after flattening are also skipped.
|
|
266
|
+
|
|
267
|
+
## Where Claude Code stores sessions
|
|
268
|
+
|
|
269
|
+
```
|
|
270
|
+
~/.claude/projects/
|
|
271
|
+
└── <url-encoded-project-path>/
|
|
272
|
+
└── <session-uuid>.jsonl
|
|
273
|
+
```
|
|
274
|
+
|
|
275
|
+
The project path is URL-encoded: `/home/user/myapp` becomes `-home-user-myapp`. Each session is a separate file, append-only, one JSON object per line.
|
|
276
|
+
|
|
277
|
+
## Limitations
|
|
278
|
+
|
|
279
|
+
- **Graph structure**: Claude Code sessions are directed acyclic graphs linked by `parentUuid`. This module reads lines in file order (linear), which is correct for the vast majority of sessions. Branched or multi-agent sessions may need custom traversal.
|
|
280
|
+
- **Tool call fidelity**: Most local models don't natively understand `<tool_use>` or `<tool_result>` tags. For inference-only use cases, consider stripping those blocks before passing to `apply_chat_template()`.
|
|
281
|
+
- **No streaming**: The module loads the full file into memory. For very large sessions, use `load_session()` and process records in batches.
|
|
282
|
+
- **Data quality for fine-tuning**: Sessions include failed attempts, retries, and exploratory tool calls. Blindly training on raw sessions will teach the model bad habits. Filter aggressively: keep only sessions where the final assistant turn solves the stated problem, and prefer sessions with a high ratio of `text` blocks to `tool_use` blocks unless tool-calling is your training target.
|