O
Ogard-Labs/octant
Local-first macOS workspace for Chat, Work & Code across any AI provider — your server, your data
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
- ★ 数取值
- 1 ★ · Ogard-Labs/octant · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-10 · 最近见到 2026-11-14 · 共见到 5 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 ★ · 1 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
Ogard-Labs/octant;我们收录于 2026-11-10;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。Octant
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
octant.sh
Octant is a local-first macOS workspace for Chat, Work, and Code
across many AI providers. One authoritative local server owns your Projects,
threads, memory, approvals, and history; the desktop app (and optionally an
authenticated browser or remote client) is a renderer over it. Octant runs the
providers you already have — local coding CLIs, agent SDKs, Ollama, or any
OpenAI- or Anthropic-compatible HTTP endpoint — and no core capability
requires a specific vendor or an Octant-operated cloud service.
## Modes
Chat — conversations in virtual Projects with scoped memory and no
implicit filesystem or shell authority.
Work — knowledge work confined to one user-approved folder: research
with citations, artifacts, previews, and Goals.
Code — engineering confined to one user-approved folder: approval-gated
access, managed worktrees, terminals, an editor, tests, and a thread board.
Modes are enforced on the server, not toggled in the renderer. Work and Code
are meant to do the same things under the same guardrail level; they differ
in focus, with Work hiding Git and other developer tools unless you turn them
on (the shared capability set is not built yet). Work never silently becomes
Code; moving to a linked Code thread requires explicit approval.
## Key features
Durable append-only event journal in SQLite; every projection is rebuildable
by replay, and recovery and backup go through a verified boundary.
Provider-neutral runtime: capabilities are reported honestly per provider and
mode, and unsupported operations fail closed instead of pretending.
Provider handoff mid-thread: change provider or model for the next turn with
a recorded provenance trail.
Context manifests and budgets with per-provider limits.
Shared, Project-scoped memory across threads, and a personal memory across
Projects that you can read, edit, and switch off.
Fork from here and Rewind to here on messages in Chat, Work, and Code
threads, and Markdown export that states what it could not include.
Managed subagents that run as in-process provider sessions with narrowed
authority.
Native harness for API-key and local models: Octant's own tools, authority
checks, and journal around any OpenAI- or Anthropic-compatible endpoint, with
model slots so a strong model can lead and review while cheaper ones read and
implement, an advisor that can redirect or pause a run, and the same session
view in the app, on the phone, and in octant agent.
Approval-gated Code threads with a read-only Plan mode, repository test
discovery, Git worktrees, PR view, and a runtime-derived Code board.
Plugin and skill marketplace: packages are quarantined on install, disabled
by default, and contribute no context until enabled.
App-managed browser and computer-use runtime with server-authoritative
policy.
Optional authenticated remote access (LAN or Tailscale) to a single host with
device pairing, key rotation, and revocation, administered from Settings →
Remote access on the host or the octant listener / octant pair / octant auth
commands.
Semantic themes, presets, and font controls.
Native macOS shell: borderless window, a split-tree workspace with one
surface per pane, translucent sidebar, command palette, and slash commands.
Octant is a local-first macOS workspace for Chat, Work, and Code
across many AI providers. One authoritative local server owns your Projects,
threads, memory, approvals, and history; the desktop app (and optionally an
authenticated browser or remote client) is a renderer over it. Octant runs the
providers you already have — local coding CLIs, agent SDKs, Ollama, or any
OpenAI- or Anthropic-compatible HTTP endpoint — and no core capability
requires a specific vendor or an Octant-operated cloud service.
## Modes
Chat — conversations in virtual Projects with scoped memory and no
implicit filesystem or shell authority.
Work — knowledge work confined to one user-approved folder: research
with citations, artifacts, previews, and Goals.
Code — engineering confined to one user-approved folder: approval-gated
access, managed worktrees, terminals, an editor, tests, and a thread board.
Modes are enforced on the server, not toggled in the renderer. Work and Code
are meant to do the same things under the same guardrail level; they differ
in focus, with Work hiding Git and other developer tools unless you turn them
on (the shared capability set is not built yet). Work never silently becomes
Code; moving to a linked Code thread requires explicit approval.
## Key features
Durable append-only event journal in SQLite; every projection is rebuildable
by replay, and recovery and backup go through a verified boundary.
Provider-neutral runtime: capabilities are reported honestly per provider and
mode, and unsupported operations fail closed instead of pretending.
Provider handoff mid-thread: change provider or model for the next turn with
a recorded provenance trail.
Context manifests and budgets with per-provider limits.
Shared, Project-scoped memory across threads, and a personal memory across
Projects that you can read, edit, and switch off.
Fork from here and Rewind to here on messages in Chat, Work, and Code
threads, and Markdown export that states what it could not include.
Managed subagents that run as in-process provider sessions with narrowed
authority.
Native harness for API-key and local models: Octant's own tools, authority
checks, and journal around any OpenAI- or Anthropic-compatible endpoint, with
model slots so a strong model can lead and review while cheaper ones read and
implement, an advisor that can redirect or pause a run, and the same session
view in the app, on the phone, and in octant agent.
Approval-gated Code threads with a read-only Plan mode, repository test
discovery, Git worktrees, PR view, and a runtime-derived Code board.
Plugin and skill marketplace: packages are quarantined on install, disabled
by default, and contribute no context until enabled.
App-managed browser and computer-use runtime with server-authoritative
policy.
Optional authenticated remote access (LAN or Tailscale) to a single host with
device pairing, key rotation, and revocation, administered from Settings →
Remote access on the host or the octant listener / octant pair / octant auth
commands.
Semantic themes, presets, and font controls.
Native macOS shell: borderless window, a split-tree workspace with one
surface per pane, translucent sidebar, command palette, and slash commands.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/ogard-labs-octant/)
- 来源
- github · https://github.com/Ogard-Labs/octant
- 按领域浏览
- 开源项目
- Traction
- 1 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。