anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

correctness check: https://pkg.go.dev/github.com/sst/opencode#section-readme #2026

New Issue
Closed
opened 2026-02-16 17:33:48 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 17:33:48 -05:00
Owner
Copy Link
Copy Source

Originally created by @PorcoRosso85 on GitHub (Oct 9, 2025).

Is this already correct?
https://pkg.go.dev/github.com/sst/opencode#section-readme
Persistent Storage: SQLite database for storing conversations and sessions

then, correct below? by my reverse engineering:

  • sessions saved ~/.local/share/opencode/storage/session//.json
  • The server starts up and displays the same list of repositories regardless of the current working directory or port used
Originally created by @PorcoRosso85 on GitHub (Oct 9, 2025). Is this already correct? https://pkg.go.dev/github.com/sst/opencode#section-readme `Persistent Storage: SQLite database for storing conversations and sessions` then, correct below? by my reverse engineering: - sessions saved ~/.local/share/opencode/storage/session/<hash>/<session-id>.json - The server starts up and displays the same list of repositories regardless of the current working directory or port used
yindo closed this issue 2026-02-16 17:33:48 -05:00
yindo commented 2026-02-16 17:33:48 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Oct 9, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #67: Discusses SQLite storage implementation for conversations and sessions - directly related to your question about SQLite database usage
  • #3026: Reports issues with session storage in the same location you mentioned (~/.local/share/opencode/storage/session/) and session loading problems
  • #23: Discusses current session storage architecture and mentions that sessions are currently stored in memory, not SQLite

Feel free to ignore if none of these address your specific documentation correctness question.

@github-actions[bot] commented on GitHub (Oct 9, 2025): This issue might be a duplicate of existing issues. Please check: - #67: Discusses SQLite storage implementation for conversations and sessions - directly related to your question about SQLite database usage - #3026: Reports issues with session storage in the same location you mentioned (~/.local/share/opencode/storage/session/) and session loading problems - #23: Discusses current session storage architecture and mentions that sessions are currently stored in memory, not SQLite Feel free to ignore if none of these address your specific documentation correctness question.
yindo commented 2026-02-16 17:33:48 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Oct 9, 2025):

thats a name squatter:
https://github.com/sst/opencode?tab=readme-ov-file#whats-the-other-repo

NOT opencode, so NOT accurate

@rekram1-node commented on GitHub (Oct 9, 2025): thats a name squatter: https://github.com/sst/opencode?tab=readme-ov-file#whats-the-other-repo NOT opencode, so NOT accurate
yindo commented 2026-02-16 17:33:48 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Oct 9, 2025):

no relation to this project

@rekram1-node commented on GitHub (Oct 9, 2025): no relation to this project
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2026
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?