markbennett.ca
WIP: A simple cli for daily tangled use cases and AI integration. This is for my personal use right now, but happy if others get mileage from it! :)
More README.md updates
+3
-3
+3
-3
README.md
+3
-3
README.md
···
73
73
- **Filtered JSON:** Saves tokens for LLM context windows.
74
74
- **Git Config Integration:** Treats the local .git folder as a database of configuration, reducing the need for environment variables or complex flags.
75
75
76
-
### Examples Tangled CLI Usage
76
+
## 6. Examples Tangled CLI Usage
77
77
78
78
```bash
79
79
tangled auth login (opens a browser for auth)
···
83
83
tangled issue list --json "id,title"
84
84
```
85
85
86
-
### Task Management
86
+
## 7. Task Management
87
87
88
88
We're bootstrapping task tracking with TODO.md, but will migrate all tasks into Tangled issues and dog food the product as soon as we have basic issue creation and listing working.
89
89
90
-
### Outstanding Issues
90
+
## 8. Outstanding Issues
91
91
92
92
1. Can we allow auth through the web browser, rather than just CLI username/password? This would be more secure and user-friendly.
93
93
2. The GitHub CLI manages the private keys allowing you to authenticate git operations. Can we do something similar, or will users have to manage SSH keys separately? Currently, I store my SSH keys in 1Password which signs requests for me. It would be great if tangled CLI could detect this and use it seamlessly, itentifying the user by the signed ssh key.