DeepSeek releases a GitHub coding-agent research prototype DeepSeek releases a GitHub coding-agent research prototype

Requests become tracked work

The design separates incoming events, permission decisions and execution. An accepted request becomes a ticket with a recorded scope and authorization basis. A worker receives the assignment, while subscribed discussion threads supply further context. Results return through channels such as comments and review replies. Tickets retain their identity when execution ends, allowing a later human follow-up to resume the work. A person can stop a ticket, preventing further messages from restarting that work.

Observation is the default

The default observe mode assesses inferred opportunities and records which ones it would accept, without starting them. Explicit requests from permitted people still run. Switching to auto allows inferred work when an assessment matches an enabled rule. Context arriving from a subscribed thread grants no additional authority. Before ended work resumes, the system checks whether its authorization still holds under the current policy.

The host remains the boundary

Deployment requires a separate agent GitHub identity with repository write access and a configured model provider. The setup uses a dedicated Harness profile and a local web panel. Its documented runtime requirements include Node.js 22.19 or newer in that release line, or Node.js 24 and later. GitHub Enterprise Server is outside the supported setup; the repository must be on github.com.