eliott/openwork
1
0
Fork 0
mirror of https://github.com/different-ai/openwork synced 2026-04-25 17:15:34 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
2b91b4d777431d74d21d88dbbc96f2d5fee5441a
openwork/apps/app/pr/telegram-private-bot-pairing.md
Omar McAdam 2b91b4d777 refactor: repo folder structure (#1038) 
* refactor(repo): move OpenWork apps into apps and ee layout

Rebase the monorepo layout migration onto the latest dev changes so the moved app, desktop, share, and cloud surfaces keep working from their new paths. Carry the latest deeplink, token persistence, build, Vercel, and docs updates forward to avoid stale references and broken deploy tooling.

* chore(repo): drop generated desktop artifacts

Ignore the moved Tauri target and sidecar paths so local cargo checks do not pollute the branch. Remove the accidentally committed outputs from the repo while keeping the layout migration intact.

* fix(release): drop built server cli artifact

Stop tracking the locally built apps/server/cli binary so generated server outputs do not leak into commits. Also update the release workflow to check the published scoped package name for @openwork/server before deciding whether npm publish is needed.

* fix(workspace): add stable CLI bin wrappers

Point the server and router package bins at committed wrapper scripts so workspace installs can create shims before dist outputs exist. Keep the wrappers compatible with built binaries and source checkouts to avoid Vercel install warnings without changing runtime behavior.
2026-03-19 11:41:38 -07:00

962 B
Raw Blame History

Summary

  • Add Telegram private identity mode with pairing gate so first chat must send /pair <code> before any tool-running messages are accepted.
  • Extend OpenWork server + app identity APIs to carry access and pairingCode fields.
  • Update Messaging UI to create either public or private Telegram bots, surface one-time pairing code, and label identity rows as Public/Private.

Evidence

  • UI screenshot (Chrome MCP): packages/app/pr/screenshots/telegram-private-pairing-code-mcp.png

Verification

  • pnpm --filter opencode-router typecheck
  • pnpm --filter openwork-server typecheck
  • pnpm --filter openwork-server test
  • pnpm --filter @different-ai/openwork-ui typecheck
  • pnpm --filter opencode-router build
  • pnpm --filter @different-ai/openwork-ui build

Notes

  • Telegram adapter startup with a dummy token fails expectedly with 401 Unauthorized; pairing logic and code issuance still validate via OpenWork API and UI.
Reference in New Issue View Git Blame Copy Permalink