CopilotKit / CopilotKit/outpost
Teams go-live: deploy the Teams bot
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 3
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 15
Description
The Teams bot is built and has a Dockerfile, but is not deployed. Health port 3003.
Why it matters
Teams is the channel our enterprise customers use. Until this is deployed, the highest-value channel Outpost supports is not receiving anything, and those tickets are not auto-created or routed.
Checklist
- Create the Railway service pointed at
apps/teams-bot - Set the Bot Framework app ID + password and the shared Outpost env vars
- Deploy to staging first with
SHADOW_MODE=trueand confirm it logs rather than posts - Verify
/healthon3003returns green - End-to-end: message in Teams → ticket created → routed to the on-call assignee
- Promote to production
Blocked-by note: #177 (orphaned-reply handling is Teams-only) is worth resolving before the production promotion, not before staging.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting apps/teams-bot and its Dockerfile, then identify how the service exposes the health endpoint on port 3003. Deploy to staging with SHADOW_MODE=true, verify /health and the Teams-to-ticket-to-assignee flow, and confirm the required Bot Framework and shared Outpost variables are set before production promotion. Review #177 before promoting production.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- backend, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100