Agent autocomplete in the terminal is just awful.

So we built a better one.

Files, directories, commands, skills, mcps, subagents,

double // away


(real time, not sped up)

5 months in. ~18% of everyone who downloaded Subspace is still a daily active user.

Retention isn't the problem. Distribution is.

Building was the easy part. Figuring out where our people actually live is the next grind.

subspace.build

Reason #248 why I could never go back to a terminal or IDE

My entire command line history & aliases accessible from CMD+K from anywhere.

Once you CMD+K your life is changed forever.

Subspace — All your Agents. One app. Zero amnesia. All your Agents. One app. Zero amnesia. Run Claude Code, Codex, and any agent CLI with cross-session memory workspaces with access to all your conversation history, terminals, docs, files, and a browser. Mac app, 14-day free trial.

→ subspace.build

The problem is no one wants to hit /clear. That means the next session starts from zero.

That is exactly why we built working memory in @subspacehq. When you hit /clear, the next session knows exactly where the last one left off.

Solid post from Thariq, but also I find this a little funny.

"we gave you 1M token context but you gotta know these tricks" most of which boil down to "don't use more than 300k tokens"

He's right though -- there is a very clear dumb zone.

x.com/trq212/stat...

Also shipping this release:

- Workspaces from remote branches and PRs
- Full file browser CRUD with batch ops
- JetBrains IDE support
- Native notification deep links to agent terminals
- Tab drag-and-drop reordering
- Tons more

We're a few weeks away from public launch. A LOT more coming.

CMD+SHIFT+N to open Task Capture and create a new task for the Inbox.

✅ Tasks Board

Rebuilt with flexible grouping, inline editing, and selection-to-task from agent output.

Tasks won't replace your Jira/Linear (yet) but they are super helpful for keeping track of your individual work, and the Inbox is super helpful to make sure you don't lose track.

Our users love Subspace because it organizes their projects. Timeline is another way to help you make sense of the ebb/flow of your projects. See your conversations in a timeline view alongside file changes, commits, and more.

Also -- easily restore your comments!

⌛️ Timeline

A unified feed of everything happening in your workspace. File changes, commits, agent conversations, PR activity. Review an hour of agent work in 30 seconds.

Subspace A native macOS workspace for AI coding agents. Download the free open beta.

Ship loop has massively accelerated our velocity. And because you can add custom actions to any git state, you can make the Ship Loop work exactly the way you or your team works.

www.subspace.build

🎉 New Features in v0.5.12

🚀 Ship Loop

A git state machine that watches your repo and surfaces one CTA — the right one. Commit, push, rebase, merge, open PR. When you've got 5 agents writing code across branches, you don't want to think about git. Now you don't have to.

In Subspace, you can see all your Claude Code/Codex chats, terminals, files, docs, and more in a single place. No more 12 window chaos.

Some big updates this release -- Ship Loop, Timeline, an updated Tasks Board, and tons of ux polish & bug fixes.

🔗 Link and more below!

Big @subspacehq update!

We're on a mission to make Subspace the best place to work together with Agents. Think of it as Slack for your AI team: every agent has presence, persistence, and a place to work WITH you.

makes me think true personal agents are pretty far out for most people unless one of them just builds their own versions of everything they’d normally need an api key for.

for personal agents to work for everyday people, they’ll need a way to sign up for services and get api keys for users with minimal setup. that doesn’t really exist today.

We should all start reporting the magnitude of our projects in tokens not lines of code.

The Claw is the Law

Coming soon to @subspacehq

* run your @openclaw agent(s) from any workspace or project
* view and resume OpenClaw sessions you started from that workspace
* create new OpenClaw sessions and run them side-by-side on different tasks

GitHub - Codename-Inc/spectre: SPECTRE is an agentic Coding Workflow - /Scope, /Plan, /Execute, /Clean, /Test, /Rebase, /Evaluate - that uses simply step by step product development workflow to generate high quality results from your AI Coding Agents. SPECTRE is an agentic Coding Workflow - /Scope, /Plan, /Execute, /Clean, /Test, /Rebase, /Evaluate - that uses simply step by step product development workflow to generate high quality results from...

Fixed now in v3.5.0, including adding models to subagents to improve speed/token efficiency in high certainty scenarios.

github.com/Codename-In...

Embarrassingly in my haste to package SPECTRE for release I inadvertently .gitignored ALL scripts in the SPECTRE repo instead of the one i was targeting.

So none of the hooks worked. 🤦🏻‍♂️

You live, you learn.

Full scope for clarity. Smallest version for velocity.

Here's why this matters: AI is dramatically faster when it's operating on working code.

Trying to wire too many advanced features together from nothing produces chaos. A stable v0 gives you a foundation where features start compounding instead of colliding.

Find and build the smallest working version.

This matters because describing the complete feature exposes flawed assumptions you'd miss if you started small. And you can always scope down, but building without knowing where something is headed creates compounding debt.

Once the vision is clear, flip it!

Don't edit yourself yet. Brain-dump, then use the AI to help you refine and structure your thinking until it's clear.

You are not trying to get approval from a busy human engineering team. We're in a different paradigm now - engineering resources are not the bottleneck anymore.

Here's the process I keep coming back to

Start by describing exactly how you want the feature to work - the full, ideal version.

When building products with AI, you have to un-learn some things that were ingrained in you as a product builder.

Here's a really big one - *constraining scope too early due to perceived complexity*

We're building something special at Codename. I can feel it. Subspace and New June are just the beginning.