Skip to content

soseek 0.1.0

Choose a tag to compare

@jstar0 jstar0 released this 16 Oct 17:30
· 5 commits to main since this release
v0.1.0
5ab7b3a

soseek 0.1.0 provides a self-hostable search and research service with a thin terminal client. The cloud server owns provider credentials, execution, budgets and evidence; clients use individual access tokens.

Included:

  • Go soseekd server and soseek CLI, authenticated discovery, OpenAPI, durable runs, SSE, cancellation and idempotent recovery.
  • Exa, Tavily, Firecrawl, Serper and Grok adapters; explicit provider/channel choice, multi-provider fusion and page reading.
  • A bounded Grok research planner, local inspection of saved long documents, cited answers, and an explicit fixed workflow.
  • Single-instance SQLite persistence, private user data, online backups, Docker/systemd examples and an Agent Skill.

Assets contain macOS/Linux/Windows CLI builds for ARM64 and AMD64. Linux archives also contain the server. The separate Linux AMD64 Docker archive can be loaded with gzip -dc soseek_0.1.0_linux_amd64_image.tar.gz | docker load. Check files against SHA256SUMS-0.1.0; BUILD-INFO-0.1.0.json identifies the source and server/image digests.

From a source checkout, sh scripts/install.sh --version 0.1.0 installs the CLI. Configure your own server and individual token as described in the usage guide and self-hosting guide.

Validation includes Go race tests and vet, six client targets, a 24-question live Exa/Tavily/merged baseline (72/72 tasks succeeded), real page reading, a completed Grok research sample, multi-provider research with explicit evidence gaps, public identity isolation/SSE/cancellation, and independent backup restore. See the acceptance record and baseline.

This is a single-instance release, without multi-node scheduling or high availability. Native Grok search on the tested third-party endpoint sometimes exceeded its requested internal tool limit; such runs retain evidence and actual usage, return partial, and stop later calls. Model citations still require semantic review. Credits and unknown monetary charges remain distinct from known USD costs. These observations do not establish universal search quality or upstream reliability.